Bug#922647: systemd --user no longer running

[Felipe Sateler]

On Wed, Feb 20, 2019 at 3:59 PM Eduard Bloch <edi at gmx.de> wrote:

> Hallo,
> * Felipe Sateler [Wed, Feb 20 2019, 02:46:32PM]:
>
> >      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 at 500.service. you may need root.
> >    Also, journalctl -b -p0..3 might give relevant error messages
>
> Thanks, see below. -p0..3 show "No entries" or nothing particularly
> interesting (some wrong .service file syntax from Christmas time).
>
> It seems to be not user specific, another user has the same problem - no
> running "systemd --user" after login.
>
> Most recent:
>
> Feb 08 20:38:51 zombie at-spi-bus-launcher[2625]: XIO:  fatal IO error 11
> (Resource temporarily unavailable) on X server ":0"
> Feb 08 20:38:51 zombie at-spi-bus-launcher[2625]:       after 3713
> requests (3713 known processed) with 0 events remaining.
> Feb 08 20:38:51 zombie systemd[2391]: run-rpc_pipefs.mount: Succeeded.
> Feb 08 20:38:51 zombie systemd[1]: Stopping User Manager for UID 500...
>

This is suspiciously close to the previous messages, which suggest the ones
left out are still relevant (ie, why did systemd decide to stop your user
manager).

-- 

Saludos,
Felipe Sateler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190221/f5f13d12/attachment.html>