Bug 1891286 - libinput error: event processing lagging behind by X ms, your system is too slow
Summary: libinput error: event processing lagging behind by X ms, your system is too slow
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-25 08:15 UTC by udo
Modified: 2023-05-25 16:18 UTC (History)
23 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-05-25 16:18:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description udo 2020-10-25 08:15:57 UTC
Description of problem:
On my system, with a AMD Ryzen 3400G, with 8 threads at 1.4 GHz or so at the least, running kernel.org 5.9.1. and Fedora 32 I see messages in the logs like:

/usr/libexec/gdm-x-session[3582]: (EE) event3  - LITEON Technology USB Multimedia Keyboard: client bug: event processing lagging behind by 14ms, your system is too slow


Version-Release number of selected component (if applicable):
gnome-shell-3.36.7-1.fc32.x86_64

How reproducible:
Use Fedora 32.
Check the logs every now and then, e.g. using `journalctl -b --no-hostname -o short-monotonic`.

Actual results:
[409963.114696] /usr/libexec/gdm-x-session[3582]: (EE) event3  - LITEON Technology USB Multimedia Keyboard: client bug: event processing lagging behind by 34ms, your system is too slow
[409976.538604] /usr/libexec/gdm-x-session[3582]: (EE) event3  - LITEON Technology USB Multimedia Keyboard: client bug: event processing lagging behind by 14ms, your system is too slow


Expected results:
No such messages.

Additional info:
Some googling leads me to believe that this is not a system problem but a compositer issue.
This means that on this system it means that the compisiter was perhaps not well written and/or perhaps not well enough optimized.

Comment 1 Armin Diehl 2020-11-19 08:47:52 UTC
same here on Fedora 33 (5.9.8-200.fc33.x86_64): (Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 20GB Memory)

Nov 19 09:31:36 e5 /usr/libexec/gdm-x-session[2896]: (EE) event9  - HID 046a:0023: client bug: event processing lagging behind by 32ms, your system is too slow
Nov 19 09:32:09 e5 /usr/libexec/gdm-x-session[2896]: (EE) event9  - HID 046a:0023: client bug: event processing lagging behind by 19ms, your system is too slow
...
Nov 19 09:40:15 e5 /usr/libexec/gdm-x-session[2896]: (EE) event9  - HID 046a:0023: client bug: event processing lagging behind by 30ms, your system is too slow
Nov 19 09:42:08 e5 /usr/libexec/gdm-x-session[2896]: (EE) event9  - HID 046a:0023: client bug: event processing lagging behind by 11ms, your system is too slow
Nov 19 09:42:08 e5 /usr/libexec/gdm-x-session[2896]: (EE) event9  - HID 046a:0023: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.

Bus 001 Device 013: ID 046a:0023 Cherry GmbH Keyboard

Comment 2 udo 2021-02-17 16:54:17 UTC
Feb 17 17:40:55 e6 gnome-shell[3747992]: libinput error: event4  - Logitech USB Optical Mouse: client bug: event processing lagging behind by 18ms, your system is too slow
Feb 17 17:41:02 e6 gnome-shell[3747992]: libinput error: event3  - LITEON Technology USB Multimedia Keyboard: client bug: event processing lagging behind by 11ms, your system is too slow
Feb 17 17:41:04 e6 gnome-shell[3747992]: libinput error: event3  - LITEON Technology USB Multimedia Keyboard: client bug: event processing lagging behind by 12ms, your system is too slow
Feb 17 17:45:11 e6 gnome-shell[3747992]: libinput error: event4  - Logitech USB Optical Mouse: client bug: event processing lagging behind by 13ms, your system is too slow
Feb 17 17:46:50 e6 gnome-shell[3747992]: libinput error: event4  - Logitech USB Optical Mouse: client bug: event processing lagging behind by 19ms, your system is too slow
Feb 17 17:47:13 e6 gnome-shell[3747992]: libinput error: event3  - LITEON Technology USB Multimedia Keyboard: client bug: event processing lagging behind by 41ms, your system is too slow
Feb 17 17:53:07 e6 gnome-shell[3747992]: libinput error: event4  - Logitech USB Optical Mouse: client bug: event processing lagging behind by 16ms, your system is too slow

Comment 3 udo 2021-02-18 07:24:36 UTC
After switching to wayland (the newer, leaner and meaner implementation of some gui stuff) the problem persists.
It appears the rootcause is not in xorg nor wayland, or is in both xorg and wayland).
When 8 threads and 16 GB of RAM are not enough, what can run this software without these messages?

Comment 4 ogboot 2021-02-20 22:38:24 UTC
Same, occurs in xorg and wayland when running graphical intensive app (aka vulcan based game).
3800X, 5700xt, 32GB ram.
JournalCTL and xorg log both show the same:

[   365.134] (EE) event9  - Logitech USB Receiver: client bug: event processing lagging behind by 33ms, your system is too slow
[   578.780] (EE) event9  - Logitech USB Receiver: client bug: event processing lagging behind by 18ms, your system is too slow
[   625.305] (EE) event9  - Logitech USB Receiver: client bug: event processing lagging behind by 27ms, your system is too slow
[   668.967] (EE) event9  - Logitech USB Receiver: client bug: event processing lagging behind by 31ms, your system is too slow
[   676.659] (EE) event9  - Logitech USB Receiver: client bug: event processing lagging behind by 27ms, your system is too slow
[   676.659] (EE) event9  - Logitech USB Receiver: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.

This always occurs right before crash of the 3D application.

Comment 5 udo 2021-04-26 08:52:12 UTC
Fedora 34 'upgrade', same issue.

Comment 6 udo 2021-09-20 15:05:36 UTC
We migrated from an AMD 3400g to a 5700g and still see the same bogus issue.

Comment 7 udo 2021-11-25 09:55:17 UTC
Any updates?

Comment 8 Sami Farin 2021-11-29 08:54:37 UTC
Is it possible that gnome-shell's JS garbage collection causes these delays?

Comment 9 udo 2021-11-29 09:18:51 UTC
Or USB powersave?

We do not have a LITEON keybaord but a Logitech 'standard' international keyboard.
Where does gnome get this false info from?

Comment 10 Adam Miller 2022-01-13 15:35:26 UTC
I have this same issue Fedora 35 Silverblue on an AMD Ryzen 5 PRO 2400G system with 32G of RAM.

Jan 13 08:31:58 optiplex5055 gnome-shell[1912]: libinput error: event3  - Kinesis Advantage2 Keyboard: client bug: event processing lagging behind by 28ms, your system is too slow
Jan 13 08:46:19 optiplex5055 gnome-shell[1912]: libinput error: event3  - Kinesis Advantage2 Keyboard: client bug: event processing lagging behind by 23ms, your system is too slow
Jan 13 08:53:31 optiplex5055 gnome-shell[1912]: libinput error: event7  - Logitech MX Ergo: client bug: event processing lagging behind by 29ms, your system is too slow
Jan 13 08:53:31 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce: scheduled expiry is in the past (-4ms), your system is too slow
Jan 13 08:53:31 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-17ms), your system is too slow
Jan 13 08:53:33 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce: scheduled expiry is in the past (-6ms), your system is too slow
Jan 13 08:53:33 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-19ms), your system is too slow
Jan 13 08:54:53 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-12ms), your system is too slow
Jan 13 08:54:55 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-1ms), your system is too slow
Jan 13 08:54:56 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-3ms), your system is too slow
Jan 13 08:55:04 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-9ms), your system is too slow
Jan 13 08:55:09 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce: scheduled expiry is in the past (-8ms), your system is too slow
Jan 13 08:55:09 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-21ms), your system is too slow
Jan 13 08:55:13 optiplex5055 gnome-shell[1912]: libinput error: event7  - Logitech MX Ergo: client bug: event processing lagging behind by 12ms, your system is too slow
Jan 13 08:55:13 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-0ms), your system is too slow
Jan 13 08:58:12 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-10ms), your system is too slow
Jan 13 09:14:17 optiplex5055 gnome-shell[1912]: libinput error: event7  - Logitech MX Ergo: client bug: event processing lagging behind by 11ms, your system is too slow
Jan 13 09:19:38 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce: scheduled expiry is in the past (-6ms), your system is too slow
Jan 13 09:19:38 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-19ms), your system is too slow
Jan 13 09:19:39 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce: scheduled expiry is in the past (-6ms), your system is too slow
Jan 13 09:19:39 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-19ms), your system is too slow
Jan 13 09:19:41 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-10ms), your system is too slow
Jan 13 09:19:46 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce: scheduled expiry is in the past (-2ms), your system is too slow
Jan 13 09:19:46 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-15ms), your system is too slow
Jan 13 09:20:02 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce: scheduled expiry is in the past (-3ms), your system is too slow
Jan 13 09:20:02 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-16ms), your system is too slow
Jan 13 09:20:03 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-3ms), your system is too slow
Jan 13 09:20:27 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce: scheduled expiry is in the past (-2ms), your system is too slow
Jan 13 09:20:27 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-15ms), your system is too slow
Jan 13 09:21:33 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-3ms), your system is too slow
Jan 13 09:21:35 optiplex5055 gnome-shell[1912]: libinput error: event7  - Logitech MX Ergo: client bug: event processing lagging behind by 25ms, your system is too slow
Jan 13 09:21:36 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce: scheduled expiry is in the past (-5ms), your system is too slow
Jan 13 09:21:36 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-18ms), your system is too slow
Jan 13 09:21:37 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-4ms), your system is too slow
Jan 13 09:21:39 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-2ms), your system is too slow
Jan 13 09:21:41 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce: scheduled expiry is in the past (-0ms), your system is too slow
Jan 13 09:21:41 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-13ms), your system is too slow
Jan 13 09:22:01 optiplex5055 gnome-shell[1912]: libinput error: event7  - Logitech MX Ergo: client bug: event processing lagging behind by 17ms, your system is too slow
Jan 13 09:22:01 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-5ms), your system is too slow
Jan 13 09:22:11 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-3ms), your system is too slow
Jan 13 09:22:42 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-7ms), your system is too slow
Jan 13 09:22:45 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-11ms), your system is too slow
Jan 13 09:22:46 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce: scheduled expiry is in the past (-6ms), your system is too slow
Jan 13 09:22:46 optiplex5055 gnome-shell[1912]: libinput error: client bug: timer event7 debounce short: scheduled expiry is in the past (-19ms), your system is too slow
Jan 13 09:26:33 optiplex5055 gnome-shell[1912]: libinput error: event3  - Kinesis Advantage2 Keyboard: client bug: event processing lagging behind by 24ms, your system is too slow

Comment 11 Michael Osborne 2022-01-21 18:01:33 UTC
I have been seeing this as well on a system which only runs vncviewer full screen, so no Gnome, no compositor

startx[512]: (EE) event3  - USBPS2 Mouse: client bug: event processing lagging behind by 11ms, your system is too slow
startx[512]: (EE) bug: timer event3 debounce short: scheduled expiry is in the past (-1ms), your system is too slow
startx[511]: (EE) event2  - USBPS2: client bug: event processing lagging behind by 17ms, your system is too slow

Comment 12 Dmitry Leonov 2022-02-03 11:08:59 UTC
I have same issue Ubuntu 21.10 (wayland). 
Feb  3 15:14:36 PC1 gnome-shell[2109]: libinput error: event10 -   USB Keyboard: client bug: event processing lagging behind by 29ms, your system is too slow

Comment 13 Gurenko Alex 2022-03-23 18:27:36 UTC
Same problem here that started not that long time ago:

Mar 23 18:53:48 kwin_wayland[2197]: kwin_libinput: Libinput: event4  - Corsair CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard: client bug: event processing lagging behind by 13ms, your system is too slow
Mar 23 18:54:00 kwin_wayland[2197]: kwin_libinput: Libinput: event4  - Corsair CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard: client bug: event processing lagging behind by 21ms, your system is too slow
Mar 23 18:55:12 kwin_wayland[2197]: kwin_libinput: Libinput: event4  - Corsair CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow
Mar 23 18:56:56 kwin_wayland[2197]: kwin_libinput: Libinput: event4  - Corsair CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard: client bug: event processing lagging behind by 30ms, your system is too slow
Mar 23 19:00:26 kwin_wayland[2197]: kwin_libinput: Libinput: event4  - Corsair CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard: client bug: event processing lagging behind by 24ms, your system is too slow
Mar 23 19:00:26 kwin_wayland[2197]: kwin_libinput: Libinput: event4  - Corsair CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.

Comment 14 Carl G. 2022-03-27 14:33:31 UTC
I have been seeing this very often on Fedora 35 and Fedora 36 beta:

gnome-shell[81874]: libinput error: event12 - Logitech G305: client bug: event processing lagging behind by 21ms, your system is too slow
gnome-shell[81874]: libinput error: event6  - USB Keyboard: client bug: event processing lagging behind by 22ms, your system is too slow
gnome-shell[81874]: libinput error: event12 - Logitech G305: client bug: event processing lagging behind by 28ms, your system is too slow
gnome-shell[81874]: libinput error: event12 - Logitech G305: client bug: event processing lagging behind by 24ms, your system is too slow
gnome-shell[81874]: libinput error: event12 - Logitech G305: client bug: event processing lagging behind by 28ms, your system is too slow
gnome-shell[81874]: libinput error: client bug: timer event12 debounce short: scheduled expiry is in the past (-21ms), your system is too slow

Desktop system, AMD R9 5900X CPU (12 cores / 24 threads)
wayland session, 144Hz display refresh rate

journalctl -b --grep="your system is too slow" | wc -l:
393 events in the last 3 days.

Comment 16 George N. White III 2022-08-28 17:16:14 UTC
Still seeing this in F36 on a 2013 iMac, using tigerVNC and keyboard from an even older iMac:


    Aug 28 13:04:42 [hostnm] gnome-shell[pid]: libinput error: event4  - Mitsumi Electric Apple Extended USB Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow
    Aug 28 13:21:59 [hostnm] gnome-shell[pid]: libinput error: event4  - Mitsumi Electric Apple Extended USB Keyboard: client bug: event processing lagging behind by 31ms, your system is too slow
    Aug 28 13:22:27 [hostnm] gnome-shell[pid]: libinput error: event4  - Mitsumi Electric Apple Extended USB Keyboard: client bug: event processing lagging behind by 28ms, your system is too slow
    Aug 28 13:22:27 [hostnm] gnome-shell[pid]: libinput error: event4  - Mitsumi Electric Apple Extended USB Keyboard: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.

Comment 17 js314592 2022-10-11 18:55:39 UTC
It can be caused by USB autosuspend which is set to only 2 seconds. It should be increased to e.g. 60 seconds or disabled.

Comment 18 js314592 2022-11-07 16:30:52 UTC
permanent increasing USB autosuspend to 20 minutes
grubby --update-kernel=ALL --args="usbcore.autosuspend=1200"

Comment 19 George N. White III 2022-11-07 17:12:46 UTC
This error seems to have stopped with the installation of the 6.0.5 kernel in Fedora 36.  It was happening multiple times a day before the update, have not yet seen it in November.

Comment 20 Gurenko Alex 2022-11-07 17:34:00 UTC
I am also running kernel 6.0.x for a few weeks on F37 and also don't see those messages anymore, but I've missed the point when the stopped, I'm currently on 6.0.7-301 kernel build

Comment 21 Ben Cotton 2023-04-25 16:40:45 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 22 Ludek Smid 2023-05-25 16:18:39 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.