Bug 314990

Summary: Screen lock unlocker disables "Blank screen" screensaver
Product: [Unmaintained] kscreensaver Reporter: Maciej J . Woloszyk <matofesi>
Component: locker-qmlAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED INTENTIONAL    
Severity: normal CC: mgraesslin, tobias-inet00
Priority: NOR    
Version: 4.10.0   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Maciej J . Woloszyk 2013-02-12 13:10:20 UTC 
I use "Blank screen" as my screensaver. It worked until yesterday when I updated my KDE to 4.10.0. Now when I select screensaver as a lock method and "Blank screen" as a screensaver and click on lock icon or set the timeout and wait I get a blank screen for just a moment and then unlock screen shows - even though I didn't set the "require password" option. If screen was locked I need to unlock it but if it started as timeout unlocker disappears after moving mouse or touching keyboard.


Reproducible: Always

Steps to Reproduce:
1. Set screen locker mode to screensaver and select "Blank screen" as screensaver
2. Click lock screen button or press ctrl+alt+l or set some timeout and wait for it to trigger.
Actual Results:  
Instead of blank screen unlocker is displayed

Expected Results:  
Blank screen should be shown and unlocker should be displayed on mouse/keyboard action only if screen was locked.
Comment 1 Tobias Langner 2013-06-05 08:42:05 UTC 
I can confirm this bug. The same happens for me with KDE 4.10.2 under Kubuntu 13.04. It is really annoying since I usually prefer to blank my screen when I don't want to be distracted and I don't want to enter a password each time to unlock it...
Comment 2 Martin Flöser 2015-01-23 14:25:42 UTC 
The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this bug report won't be implemented as it doesn't apply to our current version any more.

I want to thank you for your bug report and for helping improving the quality of our software and I'm sorry that we were not able to provide a fix before we retired the affected component.