Chromium doesn't start pulseaudio if pulseaudio isn't running

  • Open
  • quality assurance status badge
Details
2 participants
  • Maxim Cournoyer
  • pkill9
Owner
unassigned
Submitted by
pkill9
Severity
normal
P
P
pkill9 wrote on 17 Apr 2020 01:14
(address . bug-guix@gnu.org)
20200417001429.09fb8ba1@runbox.com
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.
M
M
Maxim Cournoyer wrote on 18 Apr 2020 06:09
(name . pkill9)(address . pkill9@runbox.com)(address . 40675@debbugs.gnu.org)
87eesll9iy.fsf@gmail.com
pkill9 <pkill9@runbox.com> writes:

Toggle quote (4 lines)
> 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
M
M
maxim.cournoyer wrote on 14 Aug 2020 05:00
(name . pkill9)(address . pkill9@runbox.com)(address . 40675@debbugs.gnu.org)
87sgcqszh9.fsf@hurd.i-did-not-set--mail-host-address--so-tickle-me
Hello,

pkill9 <pkill9@runbox.com> writes:

Toggle quote (4 lines)
> 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

?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 40675@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 40675
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch