Summary: | "libinput bug: timer offset negative" keeps coming up in syslog | ||
---|---|---|---|
Product: | Wayland | Reporter: | cooks.go.hungry |
Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | cooks.go.hungry, peter.hutterer |
Version: | 1.2.x | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
cooks.go.hungry
2016-06-01 17:48:16 UTC
is this reproducible? the most common cause of this is a slow compositor/X server busy with rendering. libinput does timer setups based on event timestamps from the kernel and relies on the caller to keep calling libinput_dispatch() often enough, if that isn't the case then a 150ms timer may be set for an event from 500ms ago - resulting in an offset of -350ms from the current time. Unless you can reproduce this reliably with a specific interaction there is not much we can do here. any updates here? Closing after almost a month of no updates I've been getting a lot of this since switching to using Gnome on Wayland (from X). My system freezes completely, and I need to hard restart. Looking at /var/log/messages, I see a lot of these errors just before the freeze, plus: org.gnome.Shell.desktop[2961]: libinput error: kernel bug: Touch jump detected and discarded. debian-x1yoga org.gnome.Shell.desktop[2961]: See https://wayland.freedesktop.org/libinput/doc/1.4.0/touchpad_jumping_cursor.html for details I'd be happy to help if you let me know how. The jumping touch is unrelated and can be ignored for this bug. But comment #1 still stands, this is almost always a slow compositor. I have the same issue and would like to help with consistent steps to reproduce the bug. Please let me know what information I can share. Here's a patch that'll make tracking things down a bit easier: https://lists.freedesktop.org/archives/wayland-devel/2017-July/034396.html I can confirm I have this on Arch Kernel 4.15.14-1-ARCH Gnome 3.28 on Wayland on Thinkpad X1 Carbon 2017 model. Libinput version is 1.10.3 Here some sample logs: libinput error: client bug: timer event17 debounce short: offset negative (-42ms) libinput error: client bug: timer event15 trackpoint: offset negative (-1720ms) Hi, @Nils Kaiser I have KDE, but I have same problem on Arch Linux (4.19.12-arch1-1-ARCH) Please see https://wayland.freedesktop.org/libinput/doc/latest/faqs.html#what-causes-the-timer-offset-negative-warning, this is almost never a libinput bug. fwiw, libinput has moved to gitlab, any future issues should be filed at https://gitlab.freedesktop.org/libinput/libinput |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.