SUMMARY In each power profile, there should be a way to automatically lock the computer when the screen is turned off by power management. Currently, you can only set a separate fixed timer for when screen locker automatically engages, but there's many downsides to this: 1. You can't have a different screen lock timeout for each power profile. 2. You can't have a setup where you can easily tell whether your laptop is locked when the screen is off. For example, my most common usecase is that I'll have my laptop on battery power with a short screen shutoff time. I'll have my laptop on a desk at work while I talk with nearby coworkers. During this time, the screen shuts off. If I later decide to go grab lunch, I have to wake up my screen just to check whether it properly locked. Most of the time, it isn't because my screen lock time is set to something longer than the power profile's screen shutoff time. I would like to have the ability to configure things so that if I see my screen is off, I can rest assured that it is locked. STEPS TO REPRODUCE 1. Go to one of the power profiles in Energy Saving 2. Notice that there's no "When screen turns off, automatically lock screen" option OBSERVED RESULT There's no "When screen turns off, automatically lock screen" option EXPECTED RESULT There's a "When screen turns off, automatically lock screen" option SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800U with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP EliteBook 845 14 inch G9 Notebook PC
This seems reasonable. I wonder whether this option would be a better fit for the "Screen Locking" configuration module though? There's already a checkbox "Lock after waking from sleep", another one could go right below it saying e.g. "Lock when screen is turned off". The functional difference would be that putting the option there makes it a global setting, rather than per power state profile. Would there be a problem with using the same behavior in all power states?
I think personally I am okay with either way, they both have pros and cons. 1. If its in screen locking, it's an easier UI choice I think. That setting controls lock screen behavior it should be in Screen Locking settings. Also having one toggle across all power profiles is just easy. 2. But, having it in a power profile means that a user can configure a different locking experience for docked / undocked modes. Like if I am in the office and it's generally a safe space and I am plugged into AC power, maybe I don't want the screen to constantly lock. However, if I am out in a cafe on battery, then I do. There's benefits to both approaches. I am not sure which one is more optimal.
(In reply to Synthetic451 from comment #2) > 2. But, having it in a power profile means that a user can configure a > different locking experience for docked / undocked modes. Like if I am in > the office and it's generally a safe space and I am plugged into AC power, > maybe I don't want the screen to constantly lock. However, if I am out in a > cafe on battery, then I do. Two data points which convinced me that there is no such thing as a generally safe space in the office, even docked at one's own cubicle: * At my last workplace, people who left their laptop unlocked had to buy doughnuts for the rest of the team if someone else managed to send a message from their Slack account. * At an earlier workplace, my dear coworker opened a text editor and pasted repeated lines of "I shall not leave my laptop unlocked" or something to that effect. I'm leaning toward the global setting :)
I would also lean towards putting it in the Screen Locking KCM. It would slot right into the existing UI quite nicely: > Lock screen automatically: [After some duration v] > [x] After waking from sleep > [x] When screen turns off
I am definitely okay with this. Would help my workflow a lot.