Quoting the libinput FAQ [0], this is generally due to a slow/overloaded Xorg/Wayland client:
"What causes the “timer offset negative” warning? libinput relies on the caller to call libinput_dispatch() whenever data is available on the epoll-fd. Doing so will process the state of all devices and can trigger some timers to be set (e.g. palm detection, tap-to-click, disable-while-typing, etc.). Internally, libinput’s time offsets are always based on the event time of the triggering event. For example, a touch event with time T may trigger a timer for the time T + 180ms. When setting a timer, libinput checks the wall clock time to ensure that this time T + offset is still in the future. If not, the warning is logged. When this warning appears, it simply means that too much time has passed between the event occurring (and the epoll-fd triggering) and the current time. In almost all cases this is an indication of the caller being overloaded and not handling events as speedily as required. The warning has no immediate effect on libinput’s behavior but some of the functionality that relies on the timer may be impeded (e.g. palms are not detected as they should be)." Francois [0] https://wayland.freedesktop.org/libinput/doc/latest/faqs.html#what-causes-the-timer-offset-negative-warning -- https://fmarier.org/
