https://bugs.kde.org/show_bug.cgi?id=515877
--- Comment #7 from [email protected] --- I'm not sure I understand, apologies if I'm being dense. According to https://bugs.kde.org/show_bug.cgi?id=472319 this behavior is not intentional, right? It seems to involve waking the screen, not just the input field being invisible/inactive. Also, when switching from wayland to X11 the behavior is different. In other words, using X11, when I lock the screen, press escape to blank it the first character I press both wakes/unblanks the screens *and* is used as the first character to the password input field. Is this behavior (which is new from my POV coming for X11) expected due to technical limitations around wayland, or is it expected because the UX is as expected? I'm just one user, but this change means that I need to wait 5-10 seconds before I can log in whereas before I could simply start typing my password and be logged in when the screens finished waking up. At least one of my screens is quite slow to wake. -- You are receiving this mail because: You are watching all bug changes.
