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.
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.