Bug 2831 - no sound/mic permanently if speakers/microphone isn't connected when client connects
: no sound/mic permanently if speakers/microphone isn't connected when client c...
Status: NEW
: ThinLinc
: pre-1.0
: PC Windows
: P2 Enhancement
: LowPrio
Assigned To:
  Show dependency treegraph
Reported: 2008-07-01 14:26 by
Modified: 2017-03-28 13:33 (History)
Acceptance Criteria:



You need to log in before you can comment on or make changes to this bug.

Description From cendio 2008-07-01 14:26:28
Windows Vista has the nice new feature of sound cards being removed whenever it
detects that speaker or microphone isn't connected. That means that Pulseaudio
will fail to open the sound card, and the user will have no sound even if the
speakers are plugged back in.

I'm not sure what they were smoking when they came up with this, or how to
solve it. We might have to keep polling the connection in case something shows
up. The newer suspend features of pulseaudio might help a bit.
------- Comment #1 From cendio 2008-07-01 14:30:59 -------
Unplugging the speakers or microphone during an active session also kills the
sound until you log in again.
------- Comment #2 From cendio 2009-12-22 14:45:42 -------
Same problem with Windows 7. 
------- Comment #3 From cendio 2010-09-09 14:01:55 -------
Another fun behaviour because of this is that you get no sound unless you have
both speakers and a microphone plugged in. Just speakers is insufficient.
------- Comment #4 From cendio 2013-04-08 13:42:36 -------
Same problem with Windows 8.
------- Comment #5 From cendio 2014-08-14 12:44:53 -------
Note that the problem got mitigated in bug 3222 where we load the waveout
module twice, once for playback and once for recording. This avoids the issue
of not having a microphone plugged in. We still cannot handle hotplug properly