| Summary: | Clicking on "Save Session" breaks Shutdown, Restart and Logout in Kickoff | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | medin <med.medin.2014> |
| Component: | Session Management | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | forestix, geopapougr, grahamperrin, kde, kdedev, keplicz, kilgore.trout, lassi.vaatamoinen, natalie_clarius, nate, notmart, postix, toralf.foerster |
| Priority: | HI | ||
| Version First Reported In: | 6.1.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=449077 | ||
| Latest Commit: | https://invent.kde.org/plasma/plasma-workspace/-/commit/90131bdd34a33f8063795b766940b534b166a83e | Version Fixed/Implemented In: | 6.4.6 |
| Sentry Crash Report: | |||
|
Description
medin
2024-06-22 18:15:19 UTC
can reproduce the plasma-shutdown spawns and remains stuck forever when save session is clicked. killing plasma-shutdown makes the logout actions work again Actually i can reproduce only on a system with plasma built from kdesrc-build, where plasma-shutdown is wrongly picked from /usr/bin from the packaged version rather than the self built. This makes me suspect that it might be a packaging issue (In reply to Marco Martin from comment #3) > Actually i can reproduce only on a system with plasma built from > kdesrc-build, where plasma-shutdown is wrongly picked from /usr/bin from the > packaged version rather than the self built. > > This makes me suspect that it might be a packaging issue I don't know if I'm right, but isn't plasma-shutdown owned by plasma-workspace package? And everything is compiled by Arch at the same time? There is no external source that provides a separate plasma-shutdown binary. https://gitlab.archlinux.org/archlinux/packaging/packages/plasma-workspace/-/blob/main/PKGBUILD?ref_type=heads Happens on openSUSE Tumbleweed too. Operating System: openSUSE Tumbleweed 20240627 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.6-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B79 System Version: 4.0 Session save/restoration is all kinds of broken. Looks like Firefox is the only application remembered upon session restore, no KDE applications that I have tried so far get restarted. (In reply to Lassi Väätämöinen from comment #5) > Session save/restoration is all kinds of broken. Looks like Firefox is the > only application remembered upon session restore, no KDE applications that I > have tried so far get restarted. Just to clarify, upon auto-save session the apps are not remembered. Manually saved sessions' applications seem to be started properly after logout/login. Same problem here, at a stable hardened Gentoo with keyworded Plasma 6.2.3, Gear 24.08.3, KF 5.116.0, KF 6.8.0 If I save a session, then only DISPLAY=:0 qdbus6 org.kde.Shutdown /Shutdown org.kde.Shutdown.logout works to really log out. *** Bug 503065 has been marked as a duplicate of this bug. *** (In reply to Toralf Förster from comment #7) Bug 503065 comment 1 offers an alternative workaround. Can reproduce in: Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.4 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.1 IMHO the slightly more annoying breakage is when the restart button, for installation of updates, becomes non-effective in Discover. Workaround: log out, log in, reopen Discover, retry the restart button. Reproduced in: - Debian Stable 13.1 (Trixie): Plasma 6.3.6, Frameworks 6.13.0, Qt 6.8.2 - KDE Neon User Edition 20250911-1321 live ISO: Plasma 6.4.4, Frameworks 6.17.0, Qt 6.9.2 - KDE Neon Unstable Edition 20250901-1047 live ISO: Plasma 6.4.80, Frameworks 6.18.0, Qt 6.9.2 - Wayland and X11 sessions. This bug is present in enough different distributions that I don't think it's a packaging problem. (Or if it is, then KDE has made correct packaging unreasonably difficult.) The bad state can be entered by: - Kickoff's Save Session button (Revealed by selecting Settings: Desktop Session: Session Restore: When session was manually saved) - Running plasma-shutdown in a terminal, and leaving it running - qdbus6 org.kde.Shutdown /Shutdown org.kde.Shutdown.saveSession These things are broken in the bad state: - Log Out Kickoff button - Restart Kickoff button - Shut Down Kickoff button - qdbus6 org.kde.LogoutPrompt /LogoutPrompt org.kde.LogoutPrompt.promptLogout - qdbus6 org.kde.LogoutPrompt /LogoutPrompt org.kde.LogoutPrompt.promptReboot - qdbus6 org.kde.LogoutPrompt /LogoutPrompt org.kde.LogoutPrompt.promptShutDown - qdbus6 org.kde.LogoutPrompt /LogoutPrompt org.kde.LogoutPrompt.promptAll - The computer's power button, when configured in Power Management to show the logout screen The session can be saved without triggering the bad state by using this command: qdbus6 org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.saveCurrentSession The bad state can be cleared by killing the plasma-shutdown process. I don't see any errors in dmesg or journalctl. In summary, Plasma's Save Session button leaves the user unable cleanly shut down or exit their desktop session, and it has been broken like this for at least a year. I hope someone familiar with plasma-shutdown and ksmserver-logout-greeter internals can investigate soon. It is easy to reproduce. I can reproduce this on KDE Linux with distro-provided packages, so it doesn't seem to be caused by building the session from source. A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5831 Git commit e1b251fa874e5bb1dbb009440724621a462cd691 by David Edmundson. Committed on 22/09/2025 at 15:26. Pushed by davidedmundson into branch 'master'. plasma-shutdown: Exit after manual session save plasma-shutdwon is a DBus activated executable that is meant to run one task and exit swiftly. The call to manually save a session left the process idling. This was problematic as the logout greeter checked the presence of this process to see if an existing shutdown is in progress M +2 -1 startkde/plasma-shutdown/shutdown.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/e1b251fa874e5bb1dbb009440724621a462cd691 Git commit fe268e85669dc293bd89b0813463a201ae589614 by Nate Graham, on behalf of David Edmundson. Committed on 26/09/2025 at 20:16. Pushed by ngraham into branch 'Plasma/6.5'. plasma-shutdown: Exit after manual session save plasma-shutdwon is a DBus activated executable that is meant to run one task and exit swiftly. The call to manually save a session left the process idling. This was problematic as the logout greeter checked the presence of this process to see if an existing shutdown is in progress (cherry picked from commit e1b251fa874e5bb1dbb009440724621a462cd691) Co-authored-by: David Edmundson <kde@davidedmundson.co.uk> M +2 -1 startkde/plasma-shutdown/shutdown.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/fe268e85669dc293bd89b0813463a201ae589614 Git commit 90131bdd34a33f8063795b766940b534b166a83e by Nate Graham. Committed on 02/10/2025 at 22:01. Pushed by ngraham into branch 'Plasma/6.4'. plasma-shutdown: Exit after manual session save plasma-shutdwon is a DBus activated executable that is meant to run one task and exit swiftly. The call to manually save a session left the process idling. This was problematic as the logout greeter checked the presence of this process to see if an existing shutdown is in progress (cherry picked from commit e1b251fa874e5bb1dbb009440724621a462cd691) Co-authored-by: David Edmundson <kde@davidedmundson.co.uk> M +2 -1 startkde/plasma-shutdown/shutdown.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/90131bdd34a33f8063795b766940b534b166a83e |