https://bugs.freedesktop.org/show_bug.cgi?id=102649
--- Comment #54 from Peter Hutterer <peter.hutte...@who-t.net> ---
tbh, because dwt is timeout-based it's always a race condition waiting to
happen. That's by design, simply because we don't really have any other data
that we can work with.
Making palm detection better and working it into the tap state machine improves
things, but especially if you're triggering the timeouts or you have a device
with pressure thresholds that don't apply, then it can happen more frequently.
fwiw, you can run libinput debug-events --enable-tap --verbose on the side and
it won't affect your session at all. When it does happen you'll at least have
some info that can hint of why the palm detection didn't work.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
