Ludovic Courtès writes: > Hi Marius, > > Marius Bakke skribis: > >> On a newly-installed i7 system, Shepherd believes that the "elogind" >> service is not running. Yet there is an 'elogind-daemon' process, >> spawned by PID 1, preventing subsequent "herd start elogind" invocations >> from succeeding. > > Could you show the relevant /var/log/messages bits? That should show > when/why elogind stopped. Indeed. It was because I had 'sddm-service-type' configured, which attempted to communicate with "org.freedesktop.login1" over D-Bus, which in turn autostarted elogind before shepherd had gotten around to it.