Hello, I've found a workaround: restarting elogind via SSH resolved the issue.
I guess itt may be a race between elogind and dbus-system (elogind gets started before dbus-system is fully up, and the communication with the session bus is somehow crippled from there?). I'll experiment with the elogind service a bit, adding a dumb sleep to its start slot to see if it prevents the race. Thank you, Maxim
