bug#40675: Chromium doesn't start pulseaudio if pulseaudio isn't running

bug#40675: Chromium doesn't start pulseaudio if pulseaudio isn't running

[pkill9]

It instead seems to use Alsa directly, because when I then run
Pulseaudio, it just creates a 'dummy output'. This is annoying with the
default Pulseaudio behaviour of exiting after 20 seconds of idling.

bug#40675: Chromium doesn't start pulseaudio if pulseaudio isn't running

[Maxim Cournoyer]

pkill9 <pkill9@runbox.com> writes:

> It instead seems to use Alsa directly, because when I then run
> Pulseaudio, it just creates a 'dummy output'. This is annoying with the
> default Pulseaudio behaviour of exiting after 20 seconds of idling.

I wonder if that could explain why my mic input is always reset back to the
front port, even though I almost visit alsamixer daily to set it back to
the rear port.

Maxim

bug#40675: Chromium doesn't start pulseaudio if pulseaudio isn't running

[maxim.cournoyer]

Hello,

pkill9 <pkill9@runbox.com> writes:

> It instead seems to use Alsa directly, because when I then run
> Pulseaudio, it just creates a 'dummy output'. This is annoying with the
> default Pulseaudio behaviour of exiting after 20 seconds of idling.

I did some more tests and it seem to work fine here.  Perhaps you were
bitten by this bug [0], where a dead pulseaudio connection will not be
restarted.  If you start Chromium without any pulseaudio server running,
it will cause it to auto spawn when it requires sound access.

Perhaps you can share the exacts step you use to reproduce this? Perhaps
some interaction with other sound applications is required for the
problem to manifest itself?

Thanks!

Maxim

[0] https://bugs.chromium.org/p/chromium/issues/detail?id=968540&q=microphone%20pulseaudio&can=1