With Mageia 2, when the screen was locked I could just type my password and hit enter to unlock it. With Mageia 3, if I do that, it fails to use the first key I typed, so I have to type it again. This was reported upstream: https://bugs.kde.org/show_bug.cgi?id=314685 So far it has been ignored and still says UNCONFIRMED. Reproducible: Steps to Reproduce:
CC: (none) => balcaen.john, nicolas.lecureuilSee Also: (none) => https://bugs.kde.org/show_bug.cgi?id=314685
assigning to maintainer, because he'll be faster to see whether this got fixed upstream (Confirming that you can't just type your password any more)
Keywords: (none) => UPSTREAMCC: (none) => marja11Assignee: bugsquad => nicolas.lecureuil
Still valid in KDE 4.11.3.
Version: 3 => CauldronWhiteboard: (none) => MGA3TOO
This seems somewhat improved, but not totally fixed in KDE 4.11.4 in Cauldron. 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, even if you move the mouse first, the first key you enter is not accepted.
Just in case you didn't see, upstream posted this ridiculous message and marked it as WONTFIX. "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."
Should we thus close as WONTFIX too, as I guess we won't be fixing plasma 4 ourselves for Mageia 5 if upstream doesn't care?
Version: Cauldron => 5
I guess we could, unless someone thinks they can put on their programmer hat and fix it.
Assignee: mageia => kde
(In reply to Rémi Verschelde from comment #5) > Should we thus close as WONTFIX too, as I guess we won't be fixing plasma 4 > ourselves for Mageia 5 if upstream doesn't care? (In reply to David Walser from comment #6) > I guess we could, unless someone thinks they can put on their programmer hat > and fix it. so closing
Status: NEW => RESOLVEDResolution: (none) => WONTFIX