SUMMARY If a session is manually saved: * a subsequent attempt to logout, shut down or restart will not present the customary confirmation dialogue – the requested action will not occur. STEPS TO REPRODUCE 1. System Settings, Desktop Session 2. enable manual saving, Apply 3. take any route to a Logout button, then click 4. observe the confirmation dialogue, cancel within thirty seconds 5. save a session 6. take any route to a Logout button, then click OBSERVED RESULT 7. no dialogue 8. wait more than thirty seconds, logout does not occur 9. key Control-Alt-Delete, the logout screen does not appear 10. switch to tty3 11. restart SDDM 12. login 13. the saved session is restored. EXPECTED RESULT 7. the confirmation dialogue. SOFTWARE/OS VERSIONS Ubuntu 25.04 KDE Plasma 6.3.4 KDE Frameworks 6.12.0 Qt 6.8.3 ADDITIONAL INFORMATION Reported downstream for FreeBSD <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285062> before I began switching to Linux.
Created attachment 180467 [details] Screenshot: do not ask for confirmation WORKAROUND Adapted from <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285062#c2> (closed): * actions without delay (disable the confirmation dialogue).
I can reproduce this on git-master with the steps provided
*** Bug 503077 has been marked as a duplicate of this bug. ***
Can confirm, Beta 6.4 (2) is also affected. It is a problem because a regular user will not be able to shut down his PC anymore. Easier Steps: - Settings > Session > Desktop session - To "When session was manually saved" - Kickoff menu > Session > Save session - Log out or shut down. Nothing happens. Additional info: This command should start the logoff prompt but it's not working in this case. $ qdbus org.kde.LogoutPrompt /LogoutPrompt promptReboot This command still successfully logs you out of the session: $ qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logout
(In reply to Lenzoid from comment #4) > … a regular user will not be able to shut down … The workaround at comment #1 is fairly user-friendly, please see the screenshot.
(In reply to Graham Perrin from comment #5) > The workaround at comment #1 is fairly user-friendly, please see the > screenshot. I believe Lenzoid wasn't trying different workarounds, but doing some troubleshooting to help narrow down the root cause, so the bug can be fixed.
This appears to be a duplicate of June 2022 bug 488998, with a different product and component. Apologies for the noise, I don't know how I missed 488998. *** This bug has been marked as a duplicate of bug 488998 ***