Skip to content

Handle a touch restarting in the same evdev frame

This is a fix for what is fundamentally a kernel issue, having an ABS_MT_TRACKING_ID -1 in the same frame as an ABS_MT_TRACKING_ID 1234. But it's better to paper over this than crash later when we realised our touch count got out of sync.

CC @bentiss, @jigpu

Fixes #161 (closed)

Merge request reports