Problem Description
I’m experiencing significant keyboard input issues on Fedora 42 (kernel 6.14.5-300.fc42.x86_64) that make the system nearly unusable under certain conditions:
-
When Gnome power mode is set to ‘Balanced’ or ‘Power Saver’ (works better in ‘Performance’ mode)
-
When the system is under heavy CPU load (when compiling code or calculating ReplayGain)
The issues manifest as:
-
Repeated keystrokes
-
Delayed input response
Symptoms and Testing
I’ve conducted a simple typing test to demonstrate the problem:
Under Normal Conditions (Performance Mode, Low CPU Usage, 60°C, 3.2GHz):
The quick brown fox jumps over the lazy dog
(Types correctly with no issues)
Under Power Saving Mode (Low Load, ~10% CPU usage, 48°C, 2.4GHz):
The quick brown fox jumps over the lazy dog
The quick brown fox jumps over the lazy dog
The quick brown fox jumps over the lazy doog
The quick brown fox jumps over thee lazy dog
The quick brown fox jumps over the lazy dooooog
(Notice the extra spaces, repeated letters)
Under Heavy CPU Load (Performance Mode, 100% CPU usage, 55°C, 1.1GHz):
The qqqqqqqqqqqqqqqqquick brown fox jumps over the lazy dog
The quick brown fox jumppppppppppppppppppppppppps over thhhhhhhhhhhhhhhe lazy dog
The quick broooooooooooooooooooooooooooooooooooown fox jumps over the laaazy dog
The quick brown fox jumps over the lazyyyyyyyyyyy dog
The quick brownnnnnnnnnnnnnnnnn fox jumps over the lazy dog
The quuuuuuuuuuuuick brown fox jumps over ttttttttttttthe lazzzzzzzzzzzzzzzzy dog
The quick brown fox jumps over the lazy dog
The quick brown fox jumps ovvvvvvvvvvvvvvvvvver the lazy dog
(Severe input problems with extreme key repetition, not registering that I’ve released a key for long periods of time)
System Logs
When these issues occur, the following errors appear in the system logs:
Internal Keyboard:
May 17 16:40:40 fedora gnome-shell[30871]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
May 17 16:40:40 fedora gnome-shell[30333]: libinput error: event2 - AT Translated Set 2 keyboard: client bug: event processing lagging behind by 58ms, your system is too slow
External USB Keyboard (Logitech G610):
May 17 16:38:45 fedora gnome-shell[30871]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
May 17 16:38:45 fedora gnome-shell[30333]: libinput error: event15 - Logitech Gaming Keyboard G610: client bug: event processing lagging behind by 65ms, your system is too slow
Mouse + Keyboard Issues:
May 17 16:41:50 fedora gnome-shell[30333]: libinput error: event14 - Logitech MX Master: client bug: event processing lagging behind by 58ms, your system is too slow
May 17 16:42:54 fedora gnome-shell[30333]: libinput error: event15 - Logitech Gaming Keyboard G610: client bug: event processing lagging behind by 42ms, your system is too slow
Note About My Keyboard Settings
I’ve customized my keyboard repeat settings in GNOME Settings > Accessibility > Typing, with the ‘delay’ set to short and ‘speed’ set to fast. This setup significantly improves my typing experience and productivity. Given the capabilities of my CPU, I believe the system should be able to handle these settings without issue, even under moderate load. While I understand these settings might be contributing to the problem, I’m hoping to find a solution that allows me to maintain my preferred typing experience rather than having to adjust these settings.
Troubleshooting Already Attempted
-
Setting GNOME power mode to ‘Performance’ (reduces the frequency of the issue, but doesn’t eliminate the issue)
-
Currently forced to use ‘Performance’ power mode constantly to minimise (but not eliminate) the problem
Additional Information
-
The issue affects both internal and external keyboards
-
Also impacts mouse input, but this is less noticeable
-
The keyboard lag occurs regardless of whether USB devices are connected and regardless of power source (battery or mains)
-
I have been experiencing this issue for years on this laptop with both Intel and AMD CPUs and through multiple Fedora/GNOME versions
Hardware Specifications
-
Device: Framework Laptop 13 (AMD Ryzen 7040 Series)
-
CPU: AMD Ryzen 7 7840U with Radeon 780M Graphics (8-core, 16 threads)
-
RAM: 56 GB (35GB available at time of testing)
-
Storage: Seagate NVMe SSD (200GB free space at time of testing)
-
Graphics: AMD Radeon 780M (integrated, 6GB VRAM available at time of testing)
-
Display: Wayland compositor running at 2560x1440@75Hz
-
Input devices: Laptop keyboard, Logitech G610 keyboard, Logitech MX Master mouse
-
OS: Fedora 42 with GNOME 48.1 and Wayland 24.1.6
-
Kernel: 6.14.5-300.fc42.x86_64
Request for Help
I’m hoping someone in the community might have experienced similar issues or have knowledge about potential solutions. Specifically, I’m interested in:
-
Methods to prioritise keyboard/mouse input processing even during high CPU load
-
Known bugs with libinput or Wayland on Fedora 42
-
Possible system tuning parameters that might help (scheduler settings, I/O priorities, etc.)
-
Kernel parameters that could improve input responsiveness
-
udev rules that could improve input responsiveness
I suspect this could be related to how CPU interrupts or scheduling priorities are handled. If there’s a way to ensure that HID input handling receives higher priority than background tasks like compilation or media processing, I’d be very grateful to learn about it.
I understand this isn’t a simple issue, but I’m hoping there’s another solution besides continuing to always using Performance mode just to get reliable input. Having struggled with this issue for years across different hardware, I’m hoping that the collective knowledge of this community might help to find a solution.
I would be very grateful for any assistance you could provide with this frustrating issue, even if it’s just pointing me in the right direction. Thank you in advance for your expertise and assistance.