SUMMARY When clicking logout widget, it goes straight to shutting down. if you set it for "confirm logout", the confirmation screen still says "shutting down" but you can click the Logout icon to override. STEPS TO REPRODUCE 1. Click logout on lock/logout widget 2. 3. OBSERVED RESULT EXPECTED RESULT If "confirm logout" = "n" it starts shutting down instead of logout If "confirm logout" = "y" it show "shutting down" countdown but you can override by clicking logout. SOFTWARE/OS VERSIONS opensuse:tumbleweed:20200717 Qt: 5.15.0 KDE Frameworks: 5.72.0 - KDE Plasma: 5.19.3 - kwin 5.19.3 kmail2 5.14.3 (20.04.3) - akonadiserver 5.14.3 (20.04.3) - Kernel: 5.7.7-1-default - xf86-video-nouveau: 1.0.16 ADDITIONAL INFORMATION I thought this was fixed in 5.19.3. I've deleted the widget and reinstalled from "Add Widget" but i've no idea if its the same one or update - i don't know how to check releases or if the place where the widget is downloaded from has been updated.
Same result in latest opensuse release Plasma 5.19.4 and Frameworks 5.73.0 opensuse:tumbleweed:20200812 Qt: 5.15.0 KDE Frameworks: 5.73.0 - KDE Plasma: 5.19.4 - kwin 5.19.4 kmail2 5.14.3 (20.04.3) - akonadiserver 5.14.3 (20.04.3) - Kernel: 5.8.0-1-default - xf86-video-n
Same result in latest opensuse release Plasma 5.19.5 and Frameworks 5.73.0 opensuse:tumbleweed:20200910 Qt: 5.15.0 KDE Frameworks: 5.73.0 - KDE Plasma: 5.19.5 - kwin 5.19.5 kmail2 5.15.1 (20.08.1) - akonadiserver 5.15.1 (20.08.1) - Kernel: 5.8.7-1-default
Still shutting down with 5.20 opensuse:tumbleweed:20201014 Qt: 5.15.1 KDE Frameworks: 5.75.0 - KDE Plasma: 5.20.0 - kwin 5.20.0 kmail2 5.15.2 (20.08.2) - akonadiserver 5.15.2 (20.08.2) - Kernel: 5.8.14-1-default - xf86-video-nouveau: 1.0.16
and just to confirm, if you do this from kickoff etc. everything works fine?
(In reply to David Edmundson from comment #4) > and just to confirm, if you do this from kickoff etc. everything works fine? Yes, i can logout normally via the menus.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to Bug Janitor Service from comment #6) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! I've answered any questions posed. What "info" is being requested?
The Bug Janitor cannot know if the comment you added provides the requested information; please change the status next time you do. New information was added with comment 5; changing status for inspection.
(In reply to Christoph Feck from comment #8) > The Bug Janitor cannot know if the comment you added provides the requested > information; please change the status next time you do. > > New information was added with comment 5; changing status for inspection. apologies, didn't realise i had to change status. i just thought an email is sent to all concerned because I also receive an email if someone else updates the bug in some way.
This bug still is present in Plasma 5.20.4 (on Arch). (Me and my family inadvertently shut down our shared home box several times.) The Lock/Logout widget should respect the system setting in "Startup & Shutdown / Desktop Session / Default Leave Option”. Additional fact: Selecting "Leave" from the context menu after right clicking the desktop correctly performs the "Log out" action.
Hypothetically, would it also fix your bug to have the lock/logout widgets have explicit actions for shutdown and logout that you can enable/disable?
Proposal: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/505/diffs?commit_id=c6c1834d1dd944e7791662ef1a3cb7d403ee65aa
(In reply to David Edmundson from comment #11) > Hypothetically, would it also fix your bug to have the lock/logout widgets > have explicit actions for shutdown and logout that you can enable/disable? If i recall, it used to be configurable to show/allow shutdown/restart/logout/lock via the widget itself with or without confirmation of the action or you could just edit the config file manually. Personally, i just want a choice of logout/lock with a single click rather than go via the menus. If i need to reboot/shutdown i prefer the safety of actually having to go to the menus so i don't do it by mistake.
(In reply to BingMyBong from comment #13) > (In reply to David Edmundson from comment #11) > > Hypothetically, would it also fix your bug to have the lock/logout widgets > > have explicit actions for shutdown and logout that you can enable/disable? > > If i recall, it used to be configurable to show/allow > shutdown/restart/logout/lock via the widget itself with or without > confirmation of the action or you could just edit the config file manually. > Personally, i just want a choice of logout/lock with a single click rather > than go via the menus. > If i need to reboot/shutdown i prefer the safety of actually having to go to > the menus so i don't do it by mistake. +1
Git commit 2210d9489dc5d02dbe6145d8bc64e57af4f15a51 by David Edmundson. Committed on 18/12/2020 at 09:36. Pushed by davidedmundson into branch 'master'. [applets/lock_logout] Add explicit options for logout and reboot With the UI changes in Kicker and the logout screen over the past years the concept of "leave" with a default shutodwn action has gotten muddy. Kicker shows all the options explicitly, the logout applet has got left behind, and is currently a bit broken. The leave option currently always shutdown regardless. It's perfectly valid to want to have a short applet shortcut to log out sometimes, and shutdown in other times. This patch adds explicit options for logout and reboot, and clarified the UI presentation of shutdown to match what it currently actually does. Related: bug 402081 M +8 -0 applets/lock_logout/contents/config/main.xml M +18 -5 applets/lock_logout/contents/ui/ConfigGeneral.qml M +14 -2 applets/lock_logout/contents/ui/data.js https://invent.kde.org/plasma/plasma-workspace/commit/2210d9489dc5d02dbe6145d8bc64e57af4f15a51
*** Bug 363318 has been marked as a duplicate of this bug. ***