[solved] problems with systemd-logind, doesn't start display manager

Stef9998 · 2019-01-13 08:03:59

Hi since I just upgraded my system, I have the problem that after boot it shows a black screen with an Underscore. Then after some time the Underscore start blinking and not until then I can switch to a tty.

At tty I ran "journalctl -p 3 -xb" and got this output

-- Logs begin at Sun 2019-01-13 08:01:35 CET, end at Sun 2019-01-13 08:58:55 CET. --
Jan 13 08:43:20 stefan-desk-arch NetworkManager[614]: <error> [1547365400.9559] session-monitor: failed to create systemd-logind monitor: -2
Jan 13 08:44:51 stefan-desk-arch gnome-session-binary[674]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jan 13 08:44:51 stefan-desk-arch gnome-session-binary[674]: Unrecoverable failure in required component org.gnome.SettingsDaemon.XSettings.desktop
Jan 13 08:44:51 stefan-desk-arch gnome-session-binary[674]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Clipboard.desktop
Jan 13 08:44:51 stefan-desk-arch gnome-session-binary[674]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Keyboard.desktop
Jan 13 08:44:51 stefan-desk-arch gnome-session-binary[674]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Jan 13 08:44:51 stefan-desk-arch gnome-session-binary[674]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Power.desktop
Jan 13 08:44:51 stefan-desk-arch gnome-session-binary[674]: Unrecoverable failure in required component org.gnome.SettingsDaemon.MediaKeys.desktop
Jan 13 08:44:51 stefan-desk-arch gnome-session-binary[674]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Wacom.desktop

Then I restarted systemd-logind with "systemctl restart systemd-logind". It takes a second and then takes me to my loginscreen from gdm how it normally should be at boot.

tried reinstalling gnome and systemd

Last edited by Stef9998 (2019-01-13 17:07:39)

Trilby · 2019-01-13 15:16:27

This sounds like it could be related to one of the many issues with systemd 240. Can you try downgrading systemd to the last 239 version (not as a long-term solution, but as a diagnostic test).

Stef9998 · 2019-01-13 16:23:56

Downgraded systemd to version 239.303-1.
Works again.
Seems to be a bug with systemd 240 then.
Thanks for showing me the obvious solution

Last edited by Stef9998 (2019-01-13 16:26:38)

Trilby · 2019-01-13 16:55:25

Keep in mind, that's not much of a solution. But it does narrow down precisely where the problem is. You should check the bug tracker for related bugs against systemd 240 and - if needed - file a new one.

Systemd 240 seems to have made a lot of changes, and is causing quite a bit of trouble for users. Most of the troubles should be fixed in subsequent versions, but only if they are properly reported.

There's nothing wrong with sticking with 239 for the short term as a temporary work-around for your system until a fix comes out.

Last edited by Trilby (2019-01-13 16:56:29)

Stef9998 · 2019-01-13 17:06:10

Didn't find anything, so will file a new bug report.
Thanks for the help

once · 2019-01-15 23:20:02

they update 240.34-3 ,but still lightdm sddm can not start.
and, can not back to 239 cause libidn2 dependency.

Arch Linux

#1 2019-01-13 08:03:59

[solved] problems with systemd-logind, doesn't start display manager

#2 2019-01-13 15:16:27

Re: [solved] problems with systemd-logind, doesn't start display manager

#3 2019-01-13 16:23:56

Re: [solved] problems with systemd-logind, doesn't start display manager

#4 2019-01-13 16:55:25

Re: [solved] problems with systemd-logind, doesn't start display manager

#5 2019-01-13 17:06:10

Re: [solved] problems with systemd-logind, doesn't start display manager

#6 2019-01-15 23:20:02

Re: [solved] problems with systemd-logind, doesn't start display manager

Board footer