GNU bug report logs - #40675
Chromium doesn't start pulseaudio if pulseaudio isn't running

Previous Next

To reply to this bug, email your comments to 40675 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: pkill9 <pkill9 <at> runbox.com>
To: bug-guix <at> gnu.org
Subject: Chromium doesn't start pulseaudio if pulseaudio isn't running
Date: Fri, 17 Apr 2020 00:14:29 +0100

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.

Message #8 received at 40675 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: pkill9 <pkill9 <at> runbox.com>
Cc: 40675 <at> debbugs.gnu.org
Subject: Re: bug#40675: Chromium doesn't start pulseaudio if pulseaudio isn't
 running
Date: Sat, 18 Apr 2020 00:09:41 -0400

pkill9 <pkill9 <at> 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

Message #11 received at 40675 <at> debbugs.gnu.org (full text, mbox):

From: maxim.cournoyer <at> gmail.com
To: pkill9 <pkill9 <at> runbox.com>
Cc: 40675 <at> debbugs.gnu.org
Subject: Re: bug#40675: Chromium doesn't start pulseaudio if pulseaudio isn't
 running
Date: Thu, 13 Aug 2020 23:00:50 -0400

Hello,

pkill9 <pkill9 <at> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.