On Wed, Feb 20, 2019, 14:25 Eduard Bloch <e...@gmx.de wrote: > Hallo, > * Felipe Sateler [Mon, Feb 18 2019, 06:34:37PM]: > > Control: tags -1 moreinfo > > On Mon, Feb 18, 2019 at 5:36 PM Eduard Bloch <[1]e...@gmx.de> wrote: > > > > Package: libpam-systemd > > Version: 240-5 > > Severity: normal > > > > Hi, > > > > a few days ago some user services started failed - I mainly noticed > that > > pulseaudio was no longer available. > > This looked very strange, and while checking other systems, I saw > that > > "systemd --user" is not launched, which would have started pa and > some > > other user-session daemons. > > > > Please get the logs of user@$youruid.service. It is possible a user > unit > > is timing out, and thus failing the user manager. > > Please imagine that I, as plain user here, have no idea how to map your > suggestion to something I shall actually run, and the documentation > is partly crappy from usability POV. So trying around... > > $ systemctl --user status > Failed to read server status: Process org.freedesktop.systemd1 exited with > status 1 > $ journalctl --user > No journal files were found. > -- No entries -- > $ sudo journalctl user@$UID.service > ... > Failed to add match 'user@500.service': Das Argument ist ungültig > > Yeah, so I tried also real username instead of "user" here, etc. still > getting "invalid argument" message. Which IMHO makes sense since, as > said, the systemd user instance was not started. >
Use journalctl --unit user@500.service. you may need root. Also, journalctl -b -p0..3 might give relevant error messages Saludos, Felipe Sateler
