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

[Felipe Sateler]

Control: severity -1 normal

On Fri, Jun 21, 2019 at 4:57 PM Adam Borowski <kilobyte at angband.pl> wrote:

> Control: severity -1 grave
>

I don't think this issue is RC. However, I'm not interested in playing
severity ping pong. Please involve the release team if you think the
severity should be grave, and an update for this issue would be allowed.


> 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.
>

Sorry about that, I interpreted "haven't tested beyond a simple install
yet" as implying you would ping back once the testing had been done.
Reviewed again, it has a few issues (but mostly ok). I'd like long term to
revert the order: disable autospawn by default, and have non-systemd run
something to enable it.

Honestly, I'm a bit annoyed about all this rushing. This behaviour has been
present since 2017, and  all of a sudden this is unacceptable and needs to
be fixed less than a month before release.

-- 

Saludos,
Felipe Sateler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pulseaudio-devel/attachments/20190623/dd4516ab/attachment.html>