Bug#923203: pulseaudio: fails to start without manual configuration

Adam Borowski kilobyte at angband.pl
Fri Jun 21 21:54:21 BST 2019


Control: severity -1 grave
Control: tags -1 +patch

(patch is https://salsa.debian.org/pulseaudio-team/pulseaudio/merge_requests/5)

On Fri, Jun 21, 2019 at 11:37:48AM +0200, Tobias Hansen wrote:
> I just updated by system from stretch to buster and after that there was no sound in GNOME because pulseaudio was not started.
> It can be easily worked around by setting "autospawn = yes" in ~/.config/pulse/client.conf but it's quite an annoying regression.
> 
> Can this still be fixed for buster? Can we make it an RC bug?

It should have been tagged a long time ago, but I believe that's a good
idea.  The bug is severe -- makes the package effectively useless for a good
part of users (those on any inits other than systemd), has a pending fix,
and the fix has went through maintainer's review with no comments since 3
weeks ago.

I just did some extra tests, just in case -- upgrades work for me; and
obviously the functionality itself.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8"
⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs?
⠈⠳⣄⠀⠀⠀⠀



More information about the pkg-pulseaudio-devel mailing list