Until now when the screen was locked you could just press the password and the screen would unlock. Now if you use screen locker with a screen saver you have first to press something or move the mouse in order for the unlocker to take focus and enter the password. Reproducible: Always Steps to Reproduce: 1. Set the Screen Locker to use a Screen saver. 2. Lock the screen. Actual Results: The screen will lock as normal displaying the selected screen saver. Will pop-up the entire unlock screen (not just a little window above the screen saver) and will ignore any character before getting the focus from the screen saver. Expected Results: When Screen Locker is set to work with a screen saver it should only pop up a small form for the password (like until 4.9.x) and recognize the first character pressed.
*** Bug 315587 has been marked as a duplicate of this bug. ***
Confirmed on Mageia 3 with KDE 4.10.5. Really annoying :o( I also have dual monitors, as indicated in Bug 317136, but I don't know if that's important.
I don't have Multi monitors. I also find annoying the one bellow. https://bugs.kde.org/show_bug.cgi?id=314720
Same problem on Fedora 19, KDE SC 4.11.3 and two monitors.
I just closed related bug 317136 as things seem to be working for me. I'm setting this to NEEDSINFO; if this is not working for you in 4.11.5 please reset to [UN]CONFIRMED and/or ping the report asking someone with sufficient permission to do so.
As I noted in https://bugs.mageia.org/show_bug.cgi?id=11222 This seems somewhat improved, but not totally fixed in KDE 4.11.4 in Mageia Cauldron (soon to be Mageia 4). It seems to only be an issue when the screensaver is running, so if you move the mouse first to kill the screensaver, you can put in the password just fine. Otherwise, the first key you hit gets swallowed while the screensaver is killed, so you still have this issue. In Mageia 3 (KDE 4.10.5), even if you move the mouse first, the first key you enter is not accepted. Since Cauldron has been frozen in preparation for the Mageia 4 release, we don't have 4.11.5 yet. Would you happen to have a link to the commit in 4.11.5 that supposedly fixed this?
(In reply to comment #6) > As I noted in https://bugs.mageia.org/show_bug.cgi?id=11222 > > This seems somewhat improved, but not totally fixed in KDE 4.11.4 in Mageia > Cauldron (soon to be Mageia 4). It seems to only be an issue when the > screensaver is running, so if you move the mouse first to kill the > screensaver, you can put in the password just fine. Otherwise, the first > key you hit gets swallowed while the screensaver is killed, so you still > have this issue. Ah. Well, I'm not entirely convinced that's not a feature. Do you *really* want to start typing your password without knowing what is receiving those keystrokes? Maybe one of the plasma devs can comment. In the mean time I'll repoen, since I can confirm the above described behavior... > Would you happen to have a link to the commit in > 4.11.5 that supposedly fixed this? No, sorry, I just know that I haven't been having problems with it any more since some time. (But I don't blind type...)
When I know my screen is locked and running the screensaver, yes, I absolutely do not want to have to make extra keystrokes before I type my password.
Me too i want to start typing the password directly, as it was before.
yes that's the point of this bug
*** This bug has been confirmed by popular vote. ***
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.