Shutdown delay due to transport end point not connected

mcloaked · 2022-01-16 15:59:17

On one of my laptops I have recently had quite a few situations where there is over a minute delay in shutting down. The system is an HP Envy AMD Ryzen 4500U laptop running plasma desktop Wayland session with the sddm login manager. The relevant lines in the journal showing the delay and the logged reason is:

Jan 16 13:29:19 ryzen1 systemd[1]: Stopped Wireless service.
Jan 16 13:29:19 ryzen1 audit: BPF prog-id=0 op=UNLOAD
Jan 16 13:29:28 ryzen1 systemd-logind[630]: Failed to stop user service 'user@1000.service', ignoring: Transport endpoint is not connected                                                                  
Jan 16 13:30:47 ryzen1 systemd[1]: sddm.service: State 'stop-sigterm' timed out. Killing.
Jan 16 13:30:47 ryzen1 systemd[1]: sddm.service: Killing process 724 (sddm) with signal SIGKILL.
Jan 16 13:30:47 ryzen1 systemd[1]: sddm.service: Killing process 1325 (Xorg) with signal SIGKILL.
Jan 16 13:30:47 ryzen1 systemd[1]: sddm.service: Killing process 725 (QDBusConnection) with signal SIGKILL.
Jan 16 13:30:47 ryzen1 systemd[1]: sddm.service: Main process exited, code=killed, status=9/KILL
Jan 16 13:30:47 ryzen1 systemd[1]: sddm.service: Failed with result 'timeout'.
Jan 16 13:30:47 ryzen1 systemd[1]: Stopped Simple Desktop Display Manager.

The "Failed to stop user service 'user@1000.service', ignoring: Transport endpoint is not connected" seems to be the reason for more than a minute then passing before the sddm service times out and gets killed.

Does anyone know if there is a workaround for this to give the expected immediate shutdown behaviour that used to be the norm?

It looks possible that this commit might be the underlying reason: https://invent.kde.org/plasma/plasma-wo … uests/1177 and is due for plasma 5.24 - but I don't know if has already been merged for the next 5.23 release!

Last edited by mcloaked (2022-01-16 17:31:18)

V1del · 2022-01-16 19:15:49

Seen this as well on a wayland session. As an intermediate, you can switch TTY to 1 or wherever your SDDM is on, which will skip past the delay and shutdown properly.

mcloaked · 2022-01-16 20:08:21

Thanks V1del - I know another user who just switched to [kde-unstable] to see if this issue has been patched, and said this issue does seem to be fixed using the most recent package set. It is expected that plasma 5.24 should be released a week into February, so not too long to wait, but for anyone a bit more impatient, then accepting the unstable repo and running pacman -Syu can at least get that fix along with a bunch of other useful fixes prior to 5.24

mcloaked · 2022-01-17 20:13:01

Whilst waiting for 5,24 there is a nice list of improvements for 5.24 beta that we can look forward to when 5.24 is released - https://kde.org/announcements/plasma/5/5.23.90/

Arch Linux

#1 2022-01-16 15:59:17

Shutdown delay due to transport end point not connected

#2 2022-01-16 19:15:49

Re: Shutdown delay due to transport end point not connected

#3 2022-01-16 20:08:21

Re: Shutdown delay due to transport end point not connected

#4 2022-01-17 20:13:01

Re: Shutdown delay due to transport end point not connected

Board footer