[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Nate Graham changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Nate Graham changed: What|Removed |Added CC||andreyyash...@gmail.com --- Comment #34 from Nate Graham --- *** Bug 412212 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Michael Hohmuth changed: What|Removed |Added CC||hohm...@sax.de -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #33 from korbin.freed...@guilderlandschools.net --- I love the idea of a cancel button, in which you get to choose either display sleep, suspend, or hibernate. It would be minimalistic and easy. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #32 from Jan Przybylak --- While I support do the idea of a setting to customize which buttons are shown on the lock screen, I think it would be a viable alternative to just put a 'suspend' or 'cancel' button there. Suspending the system when the escape key is pressed would also be an option (current behaviour is showing the password prompt, which I don't think is a good reaction to pressing escape). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 drohr changed: What|Removed |Added CC||k...@jwdt.org --- Comment #31 from drohr --- +1 for this feature! I suggest to have configurable settings "Show suspend button on lock screen" and "Show shut down / restart buttons on lock screen". They could be separate due to different severity. Default could be off, so the current behavior would not change by default. There are plenty of cases, where this would be convenient: - PC wakes up randomly. - Accidentally work up my PC. - Woke up PC without knowing PW. - Left PC running to finish some processing and suspend it later. - Left PC in office and returning to the office quickly just to pick up the laptop. I do not agree to the security concerns: 1. Default behavior would not change --> I click the box, so I am aware of the risk. 2. I have my password mainly to prevent unauthorized access, not to prevent unauthorized shutdown. 3. Anyone with physical access to the machine does not need the shut down button. He can press the power button / pull the plug / remove the battery / steal it / throw it out of the window / you name it... 4. In the rare case where I really want to prevent shutdown via the button (remote KVM workstation? or whatever), I just do not click the box in the settings. 5. Shutting down / suspending other users' sessions would be prevented by the normal KDE means, just as if I click the power button while I and someone else are logged in. 6. Windows / Gnome / Mac has it without facing major security issues. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Nate Graham changed: What|Removed |Added CC||techxga...@outlook.com --- Comment #30 from Nate Graham --- *** Bug 404876 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #29 from korbin.freed...@guilderlandschools.net --- *devs -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #28 from korbin.freed...@guilderlandschools.net --- That would be a nice addition! Please add this functionality KDE devs!s! It would be much appreciated! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #27 from Jan Przybylak --- In addition to Buttons I would suggest changing the auto-suspend timer on the lock screen to something short like a minute, or at least giving the user the option to set a different timer for when the system is locked. There is no point to showing the lock screen for an hour or so. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 korbin.freed...@guilderlandschools.net changed: What|Removed |Added CC||korbin.freedman@guilderland ||schools.net --- Comment #26 from korbin.freed...@guilderlandschools.net --- Hello everyone, as a Manjaro KDE user, I find it quite annoying when I accidentally turn on my computer, and can’t suspend it within the lock screen. Gnome allows a suspend function, so I don’t see why KDE can’t as well. It gets even more annoying when I accidentally turn on my brother’s computer, because then I have to call him over to login, then suspend his system. Can we either provide an suspend to ram option on the lock screen, or honor the power button as a way to suspend the system while in the lock screen, or both? Gnome allows for either the power button, or the pause button in the top right to be used to suspend the computer while in the lock screen. Even macs allow this. If this is a concern for some who want their computers on all the time, we should provide a “disable suspend while in lock screen,” to keep those people happy. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Nate Graham changed: What|Removed |Added CC||jplx...@gmail.com --- Comment #25 from Nate Graham --- *** Bug 402318 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #24 from Sergey --- agreed with Holger -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Holger changed: What|Removed |Added CC||h.kl...@gmx.de --- Comment #23 from Holger --- (In reply to Kai Uwe Broulik from comment #6) > We removed the shutdown option and the like due to security reasons, so it > doesn't make sense to add a suspend option, I suppose? Any pointer to the discussion leading to the removal would be appreciated. To me it looks like this: - physical access beats any software = allow power off, suspend / hibernate - remote session = require password for power off, suspend / hibernate -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #22 from kolAflash --- Side note: Please add a suspend-to-ram and a suspend-to-disk (if enabled) button. Both should be configurable (guess one option for both should be OK). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Peter Wu changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=392798 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #21 from Martin Flöser --- (In reply to Simone Gaiarin from comment #20) > > We cannot. If an application asks to save a document the shutdown is stuck. > > The screen is locked and it is not possible to interact with the application > > requiring interaction. That's how session shutdown is guaranteed to work on > > Linux. > > In Linux or in KDE? How does GNOME deal with this? In X11 to be precise. See ftp://ftp.x.org/pub/X11R7.0/doc/PDF/xsmp.pdf - how and if GNOME deals with that is at least to me totally irrelevant. What matters to me is the standard we implemented. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #20 from Simone Gaiarin --- > That is not true. A long running job might get cancelled due to suspend. My > example for this is a long calculation in a science department. If we allow > suspend a competing researcher might be able to destroy the work of a > researcher. If we offer this it must be configurable. If we make it configurale, I suggest that the default is to allow to suspend. I believe that the users that require this level of security are the minority, so they need to opt-in. > > We cannot. If an application asks to save a document the shutdown is stuck. > The screen is locked and it is not possible to interact with the application > requiring interaction. That's how session shutdown is guaranteed to work on > Linux. In Linux or in KDE? How does GNOME deal with this? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #19 from Martin Flöser --- (In reply to Nate Graham from comment #18) > The more I think about it, the more I find myself agreeing that we should > *at least* have the suspend option available. That's a non-destructive > action for all use cases, and will make quite a few people happy given the > use cases we've had presented so far. That is not true. A long running job might get cancelled due to suspend. My example for this is a long calculation in a science department. If we allow suspend a competing researcher might be able to destroy the work of a researcher. If we offer this it must be configurable. > > Other familiar platforms (macOS, Windows, GNOME) also go so far as to allow > you to shut down and reboot from the lock screen, even in a multi-user > environment. They first display a scary warning declaring "This action may > cause you or other logged-in users to lose work. Are you sure you want to > proceed?" > > We might consider doing something similar, if we warn the user about the > potential consequences and only allow it for admin accounts when other users > are logged in. We cannot. If an application asks to save a document the shutdown is stuck. The screen is locked and it is not possible to interact with the application requiring interaction. That's how session shutdown is guaranteed to work on Linux. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #18 from Nate Graham --- The more I think about it, the more I find myself agreeing that we should *at least* have the suspend option available. That's a non-destructive action for all use cases, and will make quite a few people happy given the use cases we've had presented so far. Other familiar platforms (macOS, Windows, GNOME) also go so far as to allow you to shut down and reboot from the lock screen, even in a multi-user environment. They first display a scary warning declaring "This action may cause you or other logged-in users to lose work. Are you sure you want to proceed?" We might consider doing something similar, if we warn the user about the potential consequences and only allow it for admin accounts when other users are logged in. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Simone Gaiarin changed: What|Removed |Added CC||simg...@gmail.com --- Comment #17 from Simone Gaiarin --- I am also in favour of having a button on the lockscreen to suspend. Suspending by closing the lid is not enough. For example I configured the action of the laptop lid to do nothing, because I want to close it without suspending when my laptop is docked and connected to a monitor. In this case the lock screen would be shown in the second monitor, and opening and closing the lid would not suspend the laptop. Moreover I have configured the power button to lock the screen, given that I do it often. So my only option is to type the password to unlock and suspend, which is very annoying. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Ian Turner changed: What|Removed |Added CC||vec...@vectro.org --- Comment #16 from Ian Turner --- Seems odd to me that I can Switch User -> Shutdown/Suspend/Etc., but not do it directly from the screen locker. Can that be the default behavior? If allowed from the login screen, and switch user is allowed, then also allowed from the lock screen? Also, if suspend/shutdown/etc., are allowed, would be nice if kscreenlocker5 responded to the relevant ACPI keys as well. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #15 from Nate Graham --- The screen locker should be able to read the user Preference set in System Settings > Power Management > Energy Saving > "When laptop lid closed". For me on Plasma 5.11.4 it does, so I can suspend my laptop by closing the screen from kscreenlocker. But if the preference there is "Do nothing", or there is no lid because we're not a laptop, then I think adding a suspend button makes sense. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 skomorokh changed: What|Removed |Added CC||skomor...@harmless.ca -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Emre changed: What|Removed |Added CC||ereno...@hotmail.com --- Comment #14 from Emre --- +1 to this in Arch KDE Plasma 5.8. I'm using a Surface Pro 3 without a keyboard (sometimes). I want to be able to suspend and resume without logging in first. This is the default "sane" behavior in Windows. Power button or shutdown/suspend icons on screen always suspends regardless of lock screen state. This shall be the default mode in laptops which shall be disabled by an option if more security is required. Hope there are more users who try to use KDE on laptops! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 kolAflash changed: What|Removed |Added CC||kolafl...@kolahilft.de --- Comment #13 from kolAflash --- (In reply to Martin Gräßlin from comment #12) > For the record: I'm currently working on a solution which would allow to > bring suspend back in the next release. I hope I found a way to make it > secure. That would be great! In KDE 4 i used to have widgets on my lockscreen, allowing me to suspend and hibernate. But in KDE 5 / Plasma 5 this isn't possible anymore. I don't like to configure my notebook to go to standby if the display is closed. Because I like to put the notebook under my arm and go somewhere else, while the notebook is for example compiling something. But sometimes I lock my notebook when leaving the office-room without it. And when I come back, I maybe just want to suspend it, because I'm going home with it. And it's ridiculous, that I have to enter my password just to put the notebook into standby! In a very general sense of security (NOT regarding the API infrastructure in KDE): Everyone in the room can just take the battery and ac cable out of my notebook to hardly shut it down. And suspend/hibernate are even less worse than a cold shutdown. So there's really no security in protecting theses actions with the users password. Hibernating may even help if you're not in place and someone else needs to unplug/replug the power cable of your desktop pc. So he can power it down (hibernate) before he unplugs the cable. Maybe in some scenarios, the ac cable / battery may be not accessible for a user and you want to keep others from suspending/hibernating the machine. So it's maybe wise to make this options configurable. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 azr...@googlemail.com changed: What|Removed |Added CC||azr...@googlemail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #12 from Martin Gräßlin --- For the record: I'm currently working on a solution which would allow to bring suspend back in the next release. I hope I found a way to make it secure. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Serhiy Zahoriya changed: What|Removed |Added CC||serhiy@gmail.com --- Comment #11 from Serhiy Zahoriya --- It's still possible to shutdown the system physically unless it's locked somewhere away from the display and HID devices or it's a remote session. Never seen both IRL, but it's possible, yes (but why leave remote session on and locked?). More, on most systems it's even still possible to both put the machine to sleep or shutdown it by switching to a [locked] TTY console unless these ACPI events are disabled (not the default in most cases, isn't it?). So it looks illogical to me that I can put my laptop to sleep by closing the lid but not by the keyboard shortcut (are there any laptops without a sleep button on the keyboard?). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Martin Gräßlin changed: What|Removed |Added CC||ohy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Martin Gräßlin changed: What|Removed |Added Component|lockscreen |breeze-theme Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Product|ksmserver |kscreenlocker -- You are receiving this mail because: You are watching all bug changes.
