This took me a while to hunt down, but now that I've found the issue I can reproduce it every time. Here are some (not very helpful) error messages from the journal.
pam_systemd(login:session): Failed to create session: Message recipient disconnected from message bus without replying
systemd-logind.service: Unexpected error response from GetNameOwner(): Connection `terminated
This also causes other issues, a very long delay while booting, systemd user features being unavailable, and things depending on graphical.target not starting up (startx in my case).
notroot@archlinux-pc ~ >systemctl --user
failed to connect to bus no such file or directory
Disabling the service fixes all of the above issues, and re-enabling it causes them again. I wish I had more info to help track down the exact cause of this, if there is anything I can do to help diagnose the issue let me know!
vilgotf
commented
3 years ago
This took me a while to hunt down, but now that I've found the issue I can reproduce it every time. Here are some (not very helpful) error messages from the journal.
This also causes other issues, a very long delay while booting, systemd user features being unavailable, and things depending on graphical.target not starting up (startx in my case).
Disabling the service fixes all of the above issues, and re-enabling it causes them again. I wish I had more info to help track down the exact cause of this, if there is anything I can do to help diagnose the issue let me know!