If the Advanced Power Management (APM) settings are configured to lock the screen on resume, and the system goes to sleep while the screen-saver is enabled (without the password requirement), the password prompt will be ignored once the system is started back again -- the user will be able tho resume without having to enter a password. Background: I noticed the password prompt on my laptop would sometimes not get enforced when resuming from sleep mode. Reproducible: Always Steps to Reproduce: (Scree-saver and sleep durations adjusted to make it easier to reproduce) 1. Open the "Screen Locker" KCM and set it to start automatically after 1 minute with the password requirement disabled. (Tested with "Simple locker" and/or "Screen saver" option) 2. Open the "Advanced Setting" KCM and check/set the "Lock on resume" option. 3. Open the "Energy Savings" KCM and set it to "Suspend Session" after 2 minutes using "Sleep". 4. Wait idly for a minute for the screen locker/saver to kick in, and another minute for the system to go into sleep mode (suspended-to-ram). 5. Once the system is in sleep mode, power it back up. Ideally, it should prompt to for a password since you had the "lock on resume option" set. Actual Results: The system resumes with the Screenlocker window displayed (prompting for a password); however, pressing any key or moving the mouse causes the desktop to be displayed bypassing the password requirement. Expected Results: On resume, the user should be required to enter the password before the desktop session is displayed. It seems like the screen-saver settings invalidly override and disable the APM requirement to lock the screen on resume.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!