Bug#900856: enlightenment: Sound fails to work after upgrade

Felipe Sateler fsateler at debian.org
Thu Jun 21 12:34:33 BST 2018

On Wed, Jun 20, 2018, 19:51 Mike Brodbelt <mike at coruscant.org.uk> wrote:

> On 19/06/18 02:35, Ross Vandegrift wrote:
> > While upgrading a different machine from stretch -> buster, I noticed
> > the following in apt-listchanges output:
> >
> > pulseaudio (11.1-2) unstable; urgency=medium
> >
> >    * Since this version, pulseaudio disables autospawn by default on
> linux
> >      systems, and replaces that with systemd socket activation. If you
> are not
> >      using systemd, then please edit or remove
> >      /etc/pulse/client.conf.d/00-disable-autospawn.conf
> >      to re-enable it.
> >
> > Seems relevant to your issue - the grep above didn't look in
> > /etc/pulse/client.conf.d.
> Many thanks, that seems to be it, and that behaviour change is fairly
> non obvious without reading the changelog.
> Perhaps the pulseaudio postinstall script could do a better job here? It
> should be possible to detect the active init system on install, and not
> disable autospawn unless systemd is positively detected, surely.

Patches welcome. If you decide to implement this, make sure that the code
is only active with a running sysvinit (ie, don't affect chroots).  It is
not trivial, which is why I didn't implement it myself. You probably need
to integrate ucf to handle all the corner cases.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pulseaudio-devel/attachments/20180621/cd640819/attachment.html>

More information about the pkg-pulseaudio-devel mailing list