Subject: Re: bug#52051: [core-updates-frozen] cannot login ('org.freedesktop.login1' service times out)

From: Ludovic Courtès <[email-masked]>
Date: Wed, 08 Dec 2021 23:18:47 +0100

Hi,

Maxim Cournoyer <[email-masked]> skribis:

> Dec  7 15:55:02 localhost shepherd[1]: Service dbus-system has been started.
> [...]
> Dec  7 15:55:10 localhost shepherd[1]: Service ntpd has been started.
> [...]
> Dec  7 15:54:46 localhost ntpd[341]: ntpd [email-masked] Thu Jan  1 12:00:01 AM UTC 1970 (1): Starting
> [...]
> Dec  7 15:55:14 localhost shepherd[1]: Service elogind has been started.
> [...]
> Dec  7 15:55:21 localhost shepherd[1]: Service upower-daemon has been started.
> [...]
> Dec  7 15:54:51 localhost dbus-daemon[335]: [system] Activating service name='org.freedesktop.login1' requested by ':1.1' (uid=0 pid=345 comm="/gnu/store/g1qlpzcfnk2r6186al2hfqjmq9yl7qkk-upower") (using servicehelper)

The key thing here is that dbus-daemon things elogind is not running and
thus considers it has to start it, which is bound to fail.

You can display the list of services known to the DBus system bus with:

  dbus-send --system --print-reply --dest=org.freedesktop.DBus \
    /org/freedesktop/DBus org.freedesktop.DBus.ListNames

I tried in a VM that had booted fine and it shows
“org.freedesktop.login1” as expected.  Could you check what that gives
for you when the bug above shows up?

I wonder if it’s possible for there to be a race, like elogind says
“hi!” to dbus-daemon but dbus-daemon is still sleepy and doesn’t notice.
Seems hard to believe though.

If it’s reproducible, could you instrument ‘elogind-service-type’ such
that elogind is started with “strace -f -o /elogind.log -s 700”?

HTH,
Ludo’.