[SOLVED] dbus/systemd issues after hard reset

bus · 2017-09-21 11:55:15

Whenever my system experiences a hard reset, the next time it boots lots of things break. I'll list them in the order of me noticing them:

1. It takes 25 seconds to login (which is the timeout period of logind or something, IIRC)
2. X doesn't start (I use this to start it)
3. startx works alright, but pulseaudio is not running (although starts manually fine as well).
4. Running loginctl reveals that the session is invalid (output)
5. This:

$ systemctl list-unit-files --user
Failed to connect to bus: No such file or directory

6. systemd log has some stuff to say as well. Highlights include:

Sep 21 18:12:02 archbus login[859]: pam_systemd(login:session): Failed to create session: Connection timed out

Sep 21 18:13:07 archbus systemd[1]: user@1003.service: Start operation timed out. Terminating.
Sep 21 18:13:12 archbus systemd[1]: Failed to start User Manager for UID 1003.
Sep 21 18:13:12 archbus systemd[1]: user@1003.service: Unit entered failed state.
Sep 21 18:13:12 archbus systemd[1]: user@1003.service: Failed with result 'timeout'.

I have no idea what to make of this. I tried looking up all the errors, and couldn't find a similar case to mine.
My current way of fixing this is rebooting. Sometimes the issue goes away after 2-3 reboots. Sometimes 6-7. Sad state of affairs.

A year or so ago the worst thing that could happen after a hard reset is the need to run a manual fsck. But these days I have to deal with all of this every time.

Any help would be appreciated.

Last edited by bus (2017-09-21 17:30:05)

seth · 2017-09-21 16:15:17

Sep 21 18:11:34 archbus alsactl[655]: /usr/bin/alsactl: sysfs_init:48: sysfs path '/sys' is invalid
Sep 21 18:11:36 archbus connmand[670]: Cannot create /var/run/connman/resolv.conf falling back to /etc/resolv.conf

When this happens, dump the output of "mount" ...

loqs · 2017-09-21 16:34:48

Similar to https://bbs.archlinux.org/viewtopic.php … 2#p1735082

bus · 2017-09-21 17:29:53

I figured it out.

Logging in took so long because psd user service begins a crash-recovery procedure when it starts (i.e. when I login), which takes a long time because my SSD is slow and my browser profile is big, so the login time out happens.
To avoid this, I can login as root after a crash and remove psd.service from /home/user/.config/sytemd/default.target.wants, which stops psd from running at login.

I tried this just now, and the solution worked like a charm.

Arch Linux

#1 2017-09-21 11:55:15

[SOLVED] dbus/systemd issues after hard reset

#2 2017-09-21 16:15:17

Re: [SOLVED] dbus/systemd issues after hard reset

#3 2017-09-21 16:34:48

Re: [SOLVED] dbus/systemd issues after hard reset

#4 2017-09-21 17:29:53

Re: [SOLVED] dbus/systemd issues after hard reset

Board footer