IMHO this one is quite severe. For me the unlock dialog often does not show a blinking cursor, often it really has no focus. After clicking into the password lineedit the cursor won't show. And having the desktop visible 10 sec. (upstream report) after resume before the unlock dialog pops in is not the intention of a lock...
Indeed it does. I know this has been happening all through 4.10, but does this happen in 4.9.5?
It does not happen with 4.9.5. 4.10 brought a rewrite with QML. There are other issues with the lockscreen (e.g.: use QtCurve and simple locker (not Widget locker -> view the nice graphical glitches; or: <4.10 put the first keystroke into the lineedit, 4.10 uses the first keystroke to "wake up" the lockscreen) but they are minor compared to this one (and already reported).
All right, just wanted to make sure that this was in fact a regression.
Just for the record, when my system was under load during suspend I've seen similar things in earlier KDE versions too...
I talked to one of the upstream devs working on the code (Oliver Henshaw) about the "10s bug" and he says: * if the screen is visible, it's just not painted over- but it should be locked anyway * that bug should only be triggered by "either old and overloaded system or using systemd" With that knowledge I'm inclined to remove the blocker, but I'd be grateful for a second opinion from the team.
This is not a total regression here. After the suspend I can see the plasma before putting the password.
I have similar issues with KDE 4.10.1 after upgrading from 4.9.5. 4.9.5 Has been removed from portage so I can't convert back to check. But I don't remember having any of these issues: - Often there is no focus, I have to click the input field, before I can start typing - If it does gains focus, The first key press that interrupted the screensaver is ignored. - When my screensaver / locker starts and I move the mousewith the NVidia driver T the prevent locking, the focus of the application that had focus is lost - When I extend my desktop to independent lockers appear on each display. I can interact with one or the other. When I move the mouse only the screensaver on the display with the cursor is interrupted. - When I use two screens with my X server the screensaver is only started on screen 0. When I use this setup, often it is simply impossible to focus the input see my comments I added to #464058. Cheers, leipie
I can confirm this on kde-4.10.2: initially unfocused unlock dialog, some keypresses (to enter password) not detected, then all of a sudden the dialog fills in the remaining keypresses, but of course fails to unlock, as an incorrect password was given. After that the unlock dialog has focus and works as it should.
4.11.4 is in tree. Please test.
(In reply to Johannes Huber from comment #9) > 4.11.4 is in tree. Please test.
