After recent Plasma update, I must move the mouse (not click, just move) in order for the lock screen to start accepting keyboard inputs. Typing the password, pressing Esc, Enter etc. gives no reaction.
STEPS TO REPRODUCE
1. Lock the screen using Cmd + L
2. Ensure screen is black with just the current time and date showing
3. Start typing password
No response to keyboard inputs, unless mouse moved.
Password input box shows and is focused after mouse is moved.
Password input box shows upon receiving keystrokes, even if mouse is not moved.
Password can be typed in, user can log in after pressing Enter without ever touching the mouse.
Linux: Kubuntu 20.04 LTS
KDE Plasma Version: 5.18.8
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
bug has started appearing probably with this update
* New upstream bugfix release (5.18.8) (LP: #1938894)
I'm experiencing this problem on 2 different machines, and I'm not the only one:
(I'm neither of the people who posted in this thread)
*** This bug has been marked as a duplicate of bug 449857 ***
For the record, I think this is actually a duplicate of bug 439604 rather than bug 449857. The former deals with Plasma 5.18.x while the latter is about Plasma 5.24 - not entirely clear if that one could also be the same bug too.
Reasoning: I use Kubuntu Backports so and Plasma 5.18.7 was published for Kubuntu Focal (current LTS) in August 2021, so I encountered bug 439604 then. Looks like Plasma 5.18.8 was published in the standard Ubuntu repository at the end of January 2022, superseding the 5.17 package in Backports. So users like Maciej are now encountering the same bug (it is still unresolved as of Plasma 5.18).
Yeah, the bug I'm encountering is about needing to *move* the mouse to activate keyboard inputs, not *click* to gain focus. I can reproduce this on a Laptop with no external screens, and on a Desktop with 2 screens.
Thanks for the redirection Wedge009!
No worries, and I made a mistake above: I meant Plasma 5.18.7 and 5.18.8, not 5.17 and 5.18.
*** Bug 451273 has been marked as a duplicate of this bug. ***