* bug#40675: Chromium doesn't start pulseaudio if pulseaudio isn't running
@ 2020-04-16 23:14 pkill9
2020-04-18 4:09 ` Maxim Cournoyer
2020-08-14 3:00 ` maxim.cournoyer
0 siblings, 2 replies; 3+ messages in thread
From: pkill9 @ 2020-04-16 23:14 UTC (permalink / raw)
To: 40675
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#40675: Chromium doesn't start pulseaudio if pulseaudio isn't running
2020-04-16 23:14 bug#40675: Chromium doesn't start pulseaudio if pulseaudio isn't running pkill9
@ 2020-04-18 4:09 ` Maxim Cournoyer
2020-08-14 3:00 ` maxim.cournoyer
1 sibling, 0 replies; 3+ messages in thread
From: Maxim Cournoyer @ 2020-04-18 4:09 UTC (permalink / raw)
To: pkill9; +Cc: 40675
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#40675: Chromium doesn't start pulseaudio if pulseaudio isn't running
2020-04-16 23:14 bug#40675: Chromium doesn't start pulseaudio if pulseaudio isn't running pkill9
2020-04-18 4:09 ` Maxim Cournoyer
@ 2020-08-14 3:00 ` maxim.cournoyer
1 sibling, 0 replies; 3+ messages in thread
From: maxim.cournoyer @ 2020-08-14 3:00 UTC (permalink / raw)
To: pkill9; +Cc: 40675
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-08-14 3:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-16 23:14 bug#40675: Chromium doesn't start pulseaudio if pulseaudio isn't running pkill9
2020-04-18 4:09 ` Maxim Cournoyer
2020-08-14 3:00 ` maxim.cournoyer
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).