On Mon, Feb 25, 2019 at 3:12 PM Eduard Bloch <e...@gmx.de> wrote: > Control: reassign -1 systemd > > Hallo, > * Felipe Sateler [Thu, Feb 21 2019, 10:32:29AM]: > > On Wed, Feb 20, 2019 at 3:59 PM Eduard Bloch <[1]e...@gmx.de> wrote: > > 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). > > That were all recent log messages it did create in the last days before > the problem has started. The system is rebooted regularly... so I guess > there is a natural reason for stopping it? >
Please post full logs. If you don't know what you are looking for, then your editing might remove important information. Please do the following: start from a fresh boot, wait until the user manager has exited, and then get the full boot log with `sudo journalctl -b`, and attach that fully. > Anyhow, in the meantime I made some more experiments, forcing "systemd > --user" with XDG_RUNTIME_DIR set and observing what has happened or is > happening. This is strange. You don't have XDG_RUNTIME_DIR set automatically? > Really weird things. I upgraded systemd to the latest sid > version and it's still adding up. Immediately after login in lightdm, I > can check the pstree and I see an active "systemd --user" process there and > a few services started from there, like gpg agent but that's only about > a half of what I would expect, especially "pulseaudio" is not started. > When I run journalctl --unit user@500.service -b0 at that moment, it > displays "No entries". > > When I check the same a couple of minutes later, the "systemd --user" > process and the whole process subtree are gone. Vanished without any > trace (when checking with journalctl --unit, as above) and still getting > "no entries". > > Now I check the main log at the time where the weird process mass > extinction happened, and see something like the following. > > Feb 25 18:48:06 zombie NetworkManager[958]: <info> [1551116886.6200] > agent-manager: req[0x563871361240, :1.76/org.freedesktop.nm-applet/500]: > agent registered > Feb 25 18:48:15 zombie systemd[1]: NetworkManager-dispatcher.service: > Succeeded. > Feb 25 18:48:15 zombie systemd[1]: Stopping User Manager for UID 160... > This is not your uid, so this is not relevant to us. > > Anyhow, I have enough of this. > I get that you are frustrated, but please vent elsewhere. Reading this doesn't precisely make me want to spend mi little debian time debugging this issue. -- Saludos, Felipe Sateler
