SDDM misses a few seconds of keyboard input when it seems to be waiting for password

[unfa]

Hi!

Here's a typical scenario:

https://youtu.be/kUSortgFm7I

I resume my machine from suspension, it shows a "pre-login screen". I hit enter to get to the actual log-in screen and start typing my password. SDDM doesn't seem to react, despite the password input text field looking ready and active. I have to wait a few seconds until the cursor starts blinking, so I can re-type my password.

Often what happens is SDDM misses a few first characters of my password - so I have to re-type it.

It's be best if this lag could be eliminated, or if SDDM would clearly semaphor that it's not ready. Maybe don't show the password input text field at all until it's 100% ready for user input?

Right now it looks like it's ready, when it's really not and that causes user irritation.

My wife is experiencing the same problem on a different machine, and I have personally seen this on at least 3 machines. All of the computers I tested and reproduced this on run Manajro KDE.

Can anyone reproduce this?

[Pointedstick]

Any chance you can try with the Breeze theme? You're using Manjaro's fork of it ("Breath") and I'd like to rule out this being caused by a bug in that theme.

[Ultra980]

I'm on OpenSUSE MicroOS and I also have this problem, but the keyboard doesn't work at all (not even for TTYs) before it works. The cursor starts blinking instantly but the keyboard doesn't work for ~30s

[Fluff663]

I have this issue with the breeze dark theme

[Pentasis]

I have been distro hopping the past few months and been having this problem on all distos. Ubuntu, Manjaro, PopOS, Endeavour and Arch (btw)

[Ultra980]

the issue for me was that my keyboard wasn't directly connected to my PC; it was connected via the monitor

[someniatko]

My keyboard turns on its keys highlight when its initialized as an USB device by the OS. I also have this problem, and when the keyboard is unresponsive in SDDM, it's highlighting is not yet turned on. After few seconds it does turn on, so it seems the OS itself does not initialize the keyboard as a device yet.

[TheGrol]

I am also having this issue, and issue appears to be happening the same way someniatko's does, where it takes a few seconds before identifying the keyboard.

[Pentasis]

I can also confirm the keyboard (and mouse) detection delay. But I also noticed that it is somehow related to the network connection. If I disable network (wifi/cable) completely, there is no delay.