You are not logged in.
On reboot, I get a 1m30s delay while systemd(?) is waiting for a stopped job. Logs show this after the appropriate amount of time:
Nov 06 15:00:02 borgy systemd[1]: xdm-archlinux.service: State 'stop-sigterm' timed out. Killing.
Nov 06 15:00:02 borgy systemd[1]: xdm-archlinux.service: Killing process 419 (xdm) with signal SIGKILL.
Nov 06 15:00:02 borgy systemd[1]: xdm-archlinux.service: Killing process 447 (Xorg) with signal SIGKILL.
Nov 06 15:00:02 borgy systemd[1]: xdm-archlinux.service: Main process exited, code=killed, status=9/KILL
Nov 06 15:00:02 borgy systemd[1]: xdm-archlinux.service: Failed with result 'timeout'.My Googlefu is failing me. Anyone seen this one before?
Edit: this seems to happen regardless of how I shutdown, e.g. from XFCE, three-finger salute in console, or shutdown -h now.
Last edited by beej (2017-11-11 05:07:42)
Offline
xdm doesn't respond to SIGTERM, can you kill the process (SIGTERM is the default signal) from VT2 or ssh (ie. w/o shutting down)?
Offline
Went into a VC, but shutting down closed all the ttys.
So I manually tried to stop xdm from a VC:
# systemctl stop xdm-archlinux.service
UNIT LOAD ACTIVE SUB DESCRIPTION
xdm-archlinux.service loaded deactivating stop-sigterm stop X-Window Display Manager
Nov 10 20:36:53 borgy systemd[1]: Stopping X-Window Display Manager...
Nov 10 20:38:23 borgy systemd[1]: xdm-archlinux.service: State 'stop-sigterm' timed out. Killing.
Nov 10 20:38:23 borgy systemd[1]: xdm-archlinux.service: Killing process 415 (xdm) with signal SIGKILL.
Nov 10 20:38:23 borgy systemd[1]: xdm-archlinux.service: Killing process 432 (Xorg) with signal SIGKILL.
Nov 10 20:38:23 borgy systemd[1]: xdm-archlinux.service: Main process exited, code=killed, status=9/KILL
Nov 10 20:38:23 borgy systemd[1]: xdm-archlinux.service: Failed with result 'timeout'.
Nov 10 20:38:23 borgy systemd[1]: Stopped X-Window Display Manager.
UNIT LOAD ACTIVE SUB DESCRIPTION
● xdm-archlinux.service loaded failed failed X-Window Display Manager After that, I rebooted, and manually tried to SIGTERM the xdm process. It dies as expected. I could even restart it with systemctl afterwards.
Offline
So somehow xdm.service got enabled as well as xdm-archlinux.service. Not sure how that happened, since I don't recall touching this in a couple years, but the fix was
# systemctl disable xdm.service
# systemctl enable xdm-archlinux.serviceOffline