(EE) client bug: timer event3 debounce short: scheduled expiry is in the past (-28ms), your system is too slow
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libinput (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
xserver-xorg-input-libinput (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Feb 5 13:17:35 H61N-USB3 /usr/lib/
Feb 5 13:17:35 H61N-USB3 /usr/lib/
Feb 5 13:17:46 H61N-USB3 /usr/lib/
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mutter 3.36.7+
ProcVersionSign
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 5 13:19:11 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-08-26 (2355 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: Upgraded to focal on 2020-09-30 (128 days ago)
summary: |
- Seeing this error in the logs while looking for any indication of Chrome - long load time + (EE) client bug: timer event3 debounce short: scheduled expiry is in the + past (-28ms), your system is too slow |
affects: | mutter (Ubuntu) → xorg-server (Ubuntu) |
affects: | xorg-server (Ubuntu) → xserver-xorg-input-libinput (Ubuntu) |
Thanks for the bug report. That message seems to come from libinput. It's an attempt to tell you the client code (Xorg in this case) is not performing well enough.
Usually this should be considered a bug in the client (Xorg) but also it might be a poor design/assumption on the part of libinput to expect all clients to perform better. So I will assign the bug to libinput too.