Bug 98401

Summary:	USB headset sporadically not detected
Product:	PulseAudio	Reporter:	Sven <sven.koehler>
Component:	misc	Assignee:	pulseaudio-bugs
Status:	RESOLVED MOVED	QA Contact:	pulseaudio-bugs
Severity:	normal
Priority:	medium	CC:	lennart
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Sven 2016-10-23 16:11:50 UTC

Since a few version of PulseAudio (at least since 7.0), I observe the following:

I unplug my USB headset from one port and plug it into another. This usually works, until at some point, the USB headset is simply not detected by PulseAudio anymore. I can unplug it and plug it in again. The USB headset is simply ignored, regardless how often I unplug and plug it in again. It shows up in dmesg and is listed as an ALSA device.

The problem is then resolved by killing the pulse audio daemon and restarting it again, that is I do the following:
- pulseaudio --kill
- pulseaudio --start

Notice that I do not unplug the USB headset while restarting PulseAudio. The previously ignored USB headset is recognized just fine by the restarted daemon.

Comment 1 Sven 2016-10-23 16:12:14 UTC

Forgot to say that I'm using PulseAudio 9.0 on Gentoo with systemd.

Comment 2 Tanu Kaskinen 2016-10-24 17:09:52 UTC

I'd guess this is the same issue as in bug 54029. A fix for that will be released in 10.0. Please reopen if 10.0 doesn't fix the problem.

If you are familiar with building software from source, you can also try installing the git version of pulseaudio instead of waiting for 10.0.

*** This bug has been marked as a duplicate of bug 54029 ***

Comment 3 Sven 2016-10-24 18:04:23 UTC

What does this bug have to do with bug 54029 ? I have reported an issue, where the headset is working fine most of the time. But then something goes haywire and pulseaudio simply ignores the USB headset.

Bug 54029 is more like "hey my USB headset doesn't work when I plug it in the first time" and not like "hey my USB headset stops working, after I unplug it and plug it in again".

Comment 4 Tanu Kaskinen 2016-10-27 13:42:39 UTC

You're right, this might very well not be the same problem.

Can you attach a log from when the problem occurs? To get the log, here are the steps:

systemctl --user disable pulseaudio.socket
systemctl --user stop pulseaudio.service pulseaudio.socket

Run pulseaudio in a terminal:

pulseaudio -vv

To ease finding the relevant parts from the log, write "before plugging in" and "after plugging in" in the terminal where pulseaudio is running before and after plugging in the headset. Once you successfully manage to reproduce the problem, copy the text from the terminal to a file and attach it to this bug.

To restore the pulseaudio service to the normal state, run

systemctl --user enable pulseaudio.socket
systemctl --user start pulseaudio.socket

Comment 5 Sven 2017-10-22 15:32:00 UTC

Today is one of these days, where I just unplugged my USB hub, pluggin in the headset (which was previously in the USB hub), and it was not detected by PulseAudio. Or maybe it was not detected by mate's volume control applet?

Anyhow, I cannot reproduce this issue. When I want it to fail to give you guys some feedback, it doesn't occur. However, when I don't want it to fail, it fails.

Comment 6 Sven 2017-10-22 15:32:19 UTC

I'm currently using PulseAudio 10.0

Comment 7 GitLab Migration User 2018-07-30 10:30:56 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/480.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.