SUMMARY Say I'm starting my KDE (Neon Useredition) system and I wait too long while SDDM presents itself. They after some time the SDDM screen is blurred because the wait has been too long. This is typically a situation that I associate with "press any key to continue"... And indeed, when I close my eyes and press a key of my keyboard SDDM wakes up. But there also happens something else at the same time: - the "wakeup input" is also registered as input for the password input field. So to really continue I have to first delete this dot in the input field and then move on. I think that this first stroke should only be a "wakeup call" for SDDM. Perhaps this is not of the utmost importance I guess, but still it would be a little more elegant. Operating System: KDE neon 6.2 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.8.0-51-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: Dell Inc. Product Name: Latitude 5480
This is intentional; it's so you can start typing your password immediately, rather than typing a random key, using your eyeballs to make sure the text field is focused, and then typing your password. That would waste time!
Thank you for your answer. I understand that this way it could be efficient. One thing: for ex-windows users (and I hope there will be al lot the coming time) this behavior is unexpected. The paused login screen in windows sees the first keystroke as wake up and the ones following as input.
We aspire to be better than Windows, not just as bad 😎