Bug 506565 - The first letter of the keyboard is not typed after the screen turns on again from the lock screen (Wayland)
Summary: The first letter of the keyboard is not typed after the screen turns on again...
Status: RESOLVED DUPLICATE of bug 488516
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.4.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-04 02:31 UTC by jjacsan
Modified: 2025-07-09 05:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jjacsan 2025-07-04 02:31:20 UTC
In Plasma with Wayland I configured the screen to turn off and lock after 5 minutes. To "turn" the screen back on I start typing my login password, but curiously the first key corresponding to my password is not typed, but the others are. I have already checked my PC's keyboard and it is working normally, including the key itself that Plasma did not detect. To confirm my hypothesis that Plasma was not picking up the first key typed, in a similar scenario, I typed a sequence of keys different from my password and discovered that the same thing happened, Plasma did not pick up the first letter typed, but when I tested it in X11/Xorg everything worked normally.
Comment 1 Filip 2025-07-04 15:22:13 UTC
Moving to screen locking component
Comment 2 Marcus Sundman 2025-07-07 21:02:41 UTC
This worked just fine in 5, but in 6 the first letter is being ignored, so the first login attempt always fails, and then there's a delay, and swearing, and breaking the keyboard, and then you need a new keyboard, and the wife complains about the swearing and noise, and then the resulting divorce (although this happens only once per marriage), so maybe we instead could go back to how it worked in 5 where no letters were ignored.
Comment 3 Marcus Sundman 2025-07-08 17:41:41 UTC
Is this a duplicate of https://bugs.kde.org/show_bug.cgi?id=488516 ?
Comment 4 Filip 2025-07-09 05:15:03 UTC
It does look like a duplicate, thanks for finding that ticket. Let's close this one.

*** This bug has been marked as a duplicate of bug 488516 ***