Hi, Maxim Cournoyer <[email protected]> skribis:
> Nov 24 21:23:58 localhost dbus-daemon[341]: [system] Activating service > name='org.freedesktop.login1' requested by ':1.16' (uid=0 pid=324 > comm="/gnu/store/ximad0zvg12r4x0x80mvym8hzg0n33jl-shadow") (using > servicehelper) > Nov 24 21:23:58 localhost elogind[1114]: elogind is already running as PID 355 > Nov 24 21:24:11 localhost wpa_supplicant[343]: wlp4s0: CTRL-EVENT-BEACON-LOSS > Nov 24 21:24:21 localhost last message repeated 5 times > Nov 24 21:24:23 localhost dbus-daemon[341]: [system] Failed to activate > service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms) > Nov 24 21:24:23 localhost shepherd[1]: Respawning term-tty2. > Nov 24 21:24:23 localhost shepherd[1]: Service host-name has been started. > Nov 24 21:24:23 localhost shepherd[1]: Service term-tty2 has been started. > Nov 24 21:24:23 localhost wpa_supplicant[343]: wlp4s0: CTRL-EVENT-BEACON-LOSS > Nov 24 21:24:27 localhost last message repeated 3 times > Nov 24 21:26:04 localhost dbus-daemon[341]: [system] Activating service > name='org.freedesktop.login1' requested by ':1.17' (uid=0 pid=429 > comm="/gnu/store/nvvmksc9pvahqmypaz3h8mqya82vnga8-slim-1") (using > servicehelper) > Nov 24 21:26:04 localhost elogind[1127]: elogind is already running as PID 355 > Nov 24 21:26:29 localhost dbus-daemon[341]: [system] Failed to activate > service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms) It looks like elogind things it’s already running as PID 355, where the PID comes from its PID file; there’s indeed a process with this PID, but is it really elogind? Or could it be that there’s a stale PID file? Does /var/log/messages shows the very first time elogind is started at boot time? With which PID? We need to find out why dbus-daemon thinks it needs to restart elogind. Ludo’.
