I would chuck your accessibility options on the login screen, and maybe any input method that is between your keystrokes and the input target. I would have some more specifics for older gnome but these days I just use defaults all the time 😅. Do you havr more than one language installed in gnome settings? Or a language with special input modes?
this post was submitted on 01 Mar 2024
15 points (94.1% liked)
Linux
48143 readers
788 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
At work I'm on a really old version of Gnome and had the same issue. I noticed I could type consecutive characters if I added a pause of 1 to 2 seconds in between each press.
Of course this is not ideal. I finally found that some how the Accessibility option called Bouncing Keys (or Bouncy Keys?) was turned on which caused this behavior. Turning it off made things work as usual.
Not sure if this is your problem as well, but it's worth a look
I think you're onto something
https://help.gnome.org/users/gnome-help/stable/a11y-bouncekeys.html.en
Does the keyboard work as expected if you switch to a text console (eg. Ctrl+Alt+F2)?
Are you on the default stable branch?
If yes and yes, you can try reinstalling the libinput package, and make sure you don't have any libinput package installed from AUR.
Another thing you can try is to check your Gnome third party extensions if you have any, there were some issues I saw mentioned because some extensions haven't been updated to work with 45.
Does the keyboard work as expected if you switch to a text console (eg. Ctrl+Alt+F2)?
I'll try as soon as possible. But I do need to mention it only occurs at the login screen, not the lock screen. Perhaps this rules out package or extension issues, but I'll try reinstalling libinput either way, and fiddle with 3rd party extensions. Thanks for your reply
Not going to help a lot but may point to a motherboard issue - I've experienced this under Windows and a reboot has solved it.
😮
it only happens after reboot. And after that there is no problem at all