96312 – "libinput bug: timer offset negative" keeps coming up in syslog

Bug 96312 - "libinput bug: timer offset negative" keeps coming up in syslog

Summary: "libinput bug: timer offset negative" keeps coming up in syslog

Status:	RESOLVED INVALID

Alias:	None

Product:	Wayland
Classification:	Unclassified
Component:	libinput (show other bugs)
Version:	1.2.x
Hardware:	All Linux (All)

Importance:	medium normal
Assignee:	Wayland bug list
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2016-06-01 17:48 UTC by cooks.go.hungry
Modified:	2019-01-02 03:39 UTC (History)
CC List:	2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description cooks.go.hungry 2016-06-01 17:48:16 UTC

I have just recently looked in my syslog and discovered that the following message shows up a lot daily so I thought I should report it:

/usr/lib/gdm3/gdm-x-session[1707]: (EE) libinput bug: timer offset negative

I am running Ubuntu GNOME 16.04 with GNOME 3.20, more information (logs and other system information etc) can be found in my LaunchPad bug report that I made through apport: https://bugs.launchpad.net/ubuntu-gnome/+bug/1588009

Comment 1 Peter Hutterer 2016-06-01 22:29:56 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.

Comment 2 Peter Hutterer 2016-06-17 00:57:24 UTC

any updates here?

Comment 3 Peter Hutterer 2016-07-13 00:47:55 UTC

Closing after almost a month of no updates

Comment 4 termite 2016-08-15 16:49:55 UTC

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.

Comment 5 Peter Hutterer 2016-08-18 05:44:21 UTC

The jumping touch is unrelated and can be ignored for this bug.

But comment #1 still stands, this is almost always a slow compositor.

Comment 6 bahodir 2017-07-01 04:55:00 UTC

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.

Comment 7 Peter Hutterer 2017-07-03 03:54:14 UTC

Here's a patch that'll make tracking things down a bit easier: https://lists.freedesktop.org/archives/wayland-devel/2017-July/034396.html

Comment 8 Nils Kaiser 2018-04-03 19:06:17 UTC

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)

Comment 9 Tom 2018-12-28 17:29:05 UTC

Hi,
@Nils Kaiser I have KDE, but I have same problem on Arch Linux (4.19.12-arch1-1-ARCH)

Comment 10 Peter Hutterer 2019-01-02 03:39:04 UTC

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.