<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - libinput 1.3.2 freezing pointer" href="https://bugs.freedesktop.org/show_bug.cgi?id=96690#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - libinput 1.3.2 freezing pointer" href="https://bugs.freedesktop.org/show_bug.cgi?id=96690">bug 96690</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>(In reply to brent s. from <a href="show_bug.cgi?id=96690#c1">comment #1</a>) > Created <a href="attachment.cgi?id=124732" name="attach_124732" title="event1's evemu record">attachment 124732</a> <a href="attachment.cgi?id=124732&action=edit" title="event1's evemu record">[details]</a> > event1's evemu record The first event here may show the issue: E: 0.000001 0001 0145 0000 # EV_KEY / BTN_TOOL_FINGER 0 E: 0.000001 0001 014d 0001 # EV_KEY / BTN_TOOL_DOUBLETAP 1 This indicates that from the kernel's POV the device switched from single finger to two-fingers down. In libinput that usually stops pointer motion (depending on finger position it may start 2fg scrolling). Was this recording started with your fingers off the touchpad? All other BTN_TOOL_FINGER events point at a potential hardware issue, whenever the device switches to single-finger down (FINGER is 1) it immediately switches to two fingers in the subsequent event (DOUBLETAP is 1). So we either have the hw not noticing that one finger was released or in-kernel tracking getting confused.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>