<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - libinput loses track and completely stops responding during two-finger scrolling"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106113#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - libinput loses track and completely stops responding during two-finger scrolling"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106113">bug 106113</a>
from <span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span></b>
<pre><span class="quote">> when it's more obviously wrong (user is trying to scroll)</span >
pinch in libinput is pinch-and-rotate and thus includes the moving component
with it. So it's really hard to figure out what the user intended based on the
data we get from the touchpad because a pinch+move gives us the same data as a
pinch+scroll. There likely are options to improve on this but so far no-one's
found the time for it.
<span class="quote">> 2. <a href="show_bug.cgi?id=106113#c3">Comment 3</a> triggers this bug too</span >
It does. In the output there we have:
<span class="quote">> event16 - touch-size: end touch</span >
So this indicates a touch threshold issue. Having said that, immediately after
there's
<span class="quote">> event16 - button state: from BUTTON_STATE_AREA, event BUTTON_EVENT_UP
> to BUTTON_STATE_NONE</span >
which would indicate a released physical button. At that point it gets hard to
guess what really happened.
Note that I can only go on the data that the recording provides, I can't guess
what you've been doing on the touchpad. So please keep any recordings/logs as
simple and self-contained as possible.</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>