On Sun, Nov 19, 2017 at 4:35 PM, Harald Dunkel <ha...@afaics.de> wrote:
> On Sun, 19 Nov 2017 13:05:09 -0300
> Felipe Sateler <fsate...@debian.org> wrote:
>
> >
> > On this upload I switched from autospawn to systemd socket activation.
> > Are you using systemd? If so, did you reboot before noticing the problem?
> > If not, you might want to reenable autospawn as indicated in the NEWS
> file.
> >
>
> Yes, I am using systemd (because it feels like most packages don't
> work anymore without).
OK, and do you have libpam-systemd installed?
> Does pulseaudio work with good ol' sysvinit?
>
It should, but it would work best with systemd.
>
> I did reboot, of course.
> Removing /etc/pulse/client.conf.d/00-disable-autospawn.conf reenabled
> pulse audio on the next reboot.
>
>
>
Weird. could you provide the output of the following (from a boot without
audio):
systemctl --user status pulseaudio.{socket,service}
journalctl --user-unit pulseaudio.socket
journalctl --user-unit pulseaudio.service
--
Saludos,
Felipe Sateler
