Summary: | Saving a desktop session breaks the confirmation dialogue for Log Out, Shut Down, and Restart | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Graham Perrin <grahamperrin> |
Component: | kcm_smserver | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | heinrich20, kdedev, nate, strong.drum0546 |
Priority: | NOR | Keywords: | regression |
Version First Reported In: | 6.3.4 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
URL: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285062 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Screenshot: do not ask for confirmation |
Description
Graham Perrin
2025-04-20 15:12:12 UTC
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 *** |