[bug] i3lock doesn't seem to register the first couple of keypresses of password about i3lock HOT 6 CLOSED

from i3lock.

Everything gets registered in the terminal after closing, waiting and opening the laptop lid.
One thing I noticed when i3lock misses keypresses is that on the first registered keypress, all of the arcs from the missed keypresses appear in rapid succession before the arc from the first registered keypress. For example, when the first registered keypress is the third keypress made, three green arcs appear in rapid succession around the center circle.

from i3lock.

Can you try the following:

1. Start i3lock from terminal as usual.
2. Enter a few key presses to make sure i3lock has fully started and is processing key presses
3. Then close the lid, re-open, check if key presses are lost / delayed

Once i3lock enters its event loop, it’s up to X11 to deliver keypress events. If there are delays, that usually means something else is happening on the X11 level (e.g. monitor re-detection / configuration), but even so, keypresses should never get lost.

Also run i3lock --debug (but be sure to redact your password from the output), perhaps that gives us a hint as to what might be happening.

from i3lock.

Oh, and also, can you try if slock (https://tools.suckless.org/slock/) or xsecurelock (https://github.com/google/xsecurelock) exhibit the same problem on your machine?

from i3lock.

For some reason, I couldn't reproduce the issue since the last comment. I regularly update and install pacman packages, so it could have been a buggy package related to the keyboard input or laptop lid.

Now, no keypresses are lost / delayed and everything works as expected.
I tested slock on my machine and it works perfectly fine.

from i3lock.

Thank you for letting us know. I'll close this until something newer comes up.

from i3lock.