You are not logged in.
Hello Arch Community,
I'm encountering an unusual issue on my Arch Linux system where, upon unlocking from the lock screen, it seems as though the "Enter" key is being pressed repeatedly, generating infinite "Enter" events. This issue occurs in the transition phase from the lock screen to my desktop environment. I'm currently using GNOME with Wayland and GDM as the display manager.
Issue Description:
Whenever I unlock my system from the lock screen, it behaves as if the "Enter" key is stuck, creating multiple "Enter" key events. This occurs specifically during the transition from the lock screen to my desktop environment.
This peculiar behavior is not isolated to general usage or any other operations; it is distinctly triggered by the unlock process.
For the sake of completeness, the primary keyboard I'm using is a mechanical keyboard, model Ajazz/Robocop. Interestingly, I've observed a similar issue with another mechanical keyboard, the CMStorm/Quickfire, where it would rapidly hit "Enter" in a similar unlock scenario. Apparently it also happens on a very cheap $5 keyboard.
I have employed evtest and libinput debug-events to monitor keyboard events, confirming that keypresses are registered normally under typical conditions, suggesting the absence of hardware malfunctions.
Troubleshooting Steps Taken:
Verified system and all packages are up-to-date.
Used evtest to monitor keyboard events, which showed normal behavior outside the unlock scenario.
Checked GDM and GNOME settings for any unusual configurations that might affect keyboard behavior.
Reviewed system logs for any errors or warnings related to input devices or GDM but didn't find anything conclusive.
Questions:
Has anyone experienced a similar issue, or does anyone have insights into what might be causing this behavior?
Are there known issues with GDM, GNOME, or Wayland related to input device handling, especially upon waking or unlocking?
Any recommendations for further troubleshooting steps or logs that might provide more insights?
I'm grateful for any advice or guidance the community can provide on this matter. Thank you in advance for your assistance!
Last edited by renordw (2024-02-21 00:00:48)
Offline
Bizarrely enough, this behavior seems to trigger whenever I type my password very fast, and hit enter.
Whenever I type my password slowly, and hit enter a full second afterwards -- there is no infinite "Enter" event behavior.
Presumably it has something to do with me hitting enter before I have let go of the other key?
Offline
Used evtest to monitor keyboard events, which showed normal behavior outside the unlock scenario.
Have you also checked evtest during the malfunction?
Does it happen on an X11 session or from the multi-user.target (2nd link below)?
Offline