https://bugs.kde.org/show_bug.cgi?id=525911
--- Comment #1 from [email protected] --- I could reproduce it again on the same evening: ``` 21:55:59 plasma-shutdown started (org.kde.Shutdown activated) 21:59:04 ksmserver-logout-greeter: "org.kde.Shutdown D-Bus service is already registered; quitting" 22:09:45 ksmserver-logout-greeter: "org.kde.Shutdown D-Bus service is already registered; quitting" 22:16:37 ksmserver-logout-greeter: "org.kde.Shutdown D-Bus service is already registered; quitting" ``` plasma-shutdown (single process, PID stable throughout) sat idle in ppoll() the whole time, holding org.kde.Shutdown, while three separate attempts to open the logout prompt over the next ~20 minutes all bailed out immediately because the name was already taken — matching the "earlier occurrence" behavior described in the original report. Manually running: ``` busctl --user call org.kde.Shutdown /Shutdown org.kde.Shutdown logout ``` unstuck it immediately: closeSession → closeWaylandWindows completed cleanly within ~2 seconds and the machine rebooted, confirming the reboot itself had already been armed independently and was just waiting for the session to actually end. A gdb backtrace taken while it was stuck showed the main thread parked at the top of the Qt event loop (QCoreApplication::exec() → ppoll), with no synchronous call frame — consistent with an async QDBusPendingCallWatcher (e.g. for closeSession or closeWaylandWindows) whose reply never arrived, rather than a deadlock or busy loop. -- You are receiving this mail because: You are watching all bug changes.
