https://bugs.freedesktop.org/show_bug.cgi?id=88037
--- Comment #2 from Peter Hutterer <[email protected]> --- ok, found out the reason. You're starting on the far left of the touchpad, the slow movement causes palm detection to trigger. That touchpoint is then designated a palm, even if it moves around erratically after that. We mitigate this by doing movement analysis at the beginning of the touch but the slow movement you're starting makes that not trigger (200ms timeout for moving out of the zone). See this page for details: http://wayland.freedesktop.org/libinput/doc/latest/palm_detection.html I'm inclined to treat this as WONTFIX, mainly because I don't know how to make this work any other way. Palm data is so unreliable and all over the place that we can't do anything else that's reliable. To confirm: this bug should only trigger if you start on the left or right edge of the touchpad, not if you start in the middle. correct? -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ wayland-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
