On Sun, Nov 19, 2017 at 7:01 PM, Harald Dunkel <ha...@afaics.de> wrote:
> On Sun, 19 Nov 2017 17:26:16 -0300
> Felipe Sateler <fsate...@debian.org> wrote:
>
> > > 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
> >
>
> % systemctl --user status pulseaudio.{socket,service}
> Failed to get properties: Process org.freedesktop.systemd1 exited with
> status 1
> % su
> Password:
> # systemctl --user status pulseaudio.{socket,service}
> Failed to get properties: Connection reset by peer
> # journalctl --user-unit pulseaudio.socket
> -- Logs begin at Sun 2017-11-19 22:54:23 CET, end at Sun 2017-11-19
> 22:56:21 CET. --
> -- No entries --
> # journalctl --user-unit pulseaudio.service
> -- Logs begin at Sun 2017-11-19 22:54:23 CET, end at Sun 2017-11-19
> 22:56:21 CET. --
> -- No entries --
> #
>
OK. These indicate that the systemd user instances are not running. Do you
have libpam-systemd installed? If yes, could you post the output of
journalctl user@1000.service
(Assuming 1000 is the uid of your user.)
--
Saludos,
Felipe Sateler
