<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><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#c6">Comment # 6</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 <span class="vcard"><a class="email" href="mailto:brent.saner@gmail.com" title="brent s. <brent.saner@gmail.com>"> <span class="fn">brent s.</span></a>
</span></b>
<pre>(In reply to Peter Hutterer from <a href="show_bug.cgi?id=96690#c5">comment #5</a>)
> The first event here may show the issue:
<span class="quote">>
> 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?</span >
Yes; i don't think I bumped into the pad or anything either with the heel of my
thumb/palm. I tried to keep as far away from it as I could when starting. I can
always generate another one via SSH and then try to reproduce while that's
running so I can be sure I had no physical contact with the machine when
starting, but it's fairly sporadic (though often) and a little bit difficult to
reproduce intentionally.
<span class="quote">> 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.</span >
Hrm.. the hardware's fairly new (laptop was purchased/unboxed about two? three?
weeks ago). That doesn't of course rule out faulty manufacturing but it does
certainly make it being a hardware-level issue less likely, I'd presume.
Anything I can try to help narrow it down?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>