<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Touch events dropped after multiple touchpoints hit at once"
href="https://bugs.freedesktop.org/show_bug.cgi?id=67563#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Touch events dropped after multiple touchpoints hit at once"
href="https://bugs.freedesktop.org/show_bug.cgi?id=67563">bug 67563</a>
from <span class="vcard"><a class="email" href="mailto:ullysses.a.eoff@intel.com" title="U. Artie Eoff <ullysses.a.eoff@intel.com>"> <span class="fn">U. Artie Eoff</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=67563#c10">comment #10</a>)
<span class="quote">> Neil, my touch device does not report MT events. I'll open a new bug for
> the single touch bug (since it doesn't appear related to this MT issue) and
> attach my evtest output to it.</span >
(In reply to <a href="show_bug.cgi?id=67563#c4">comment #4</a>)
<span class="quote">> Not sure if it's related, but I can trigger weston to stop processing touch
> events with a single touch device, too. It's harder to trigger, but by
> rapidly tapping the screen in random places, Weston eventually gets into a
> state where it stops sending touch events to the clients.
>
> After a little debugging, I found that input.c::notify_touch() gets invoked
> with a value of WL_TOUCH_UP by evdev.c::evdev_process_key() twice in a row
> when seat->num_tp==1 prior to the first WL_TOUCH_UP. This results in
> seat->num_tp getting decremented too many times, hence halting client touch
> notifications. In other words, the number of invocations of
> notify_touch(WL_TOUCH_DOWN) and notify_touch(WL_TOUCH_UP) are not symmetric.
> Beyond this, I'm not sure what triggers evdev_process_key() to handle two
> BTN_TOUCH 0 events in a row... since evtest BTN_TOUCH 1 and BTN_TOUCH 0
> events appear to be symmetric.</span >
The single touch issue is now being tracked in <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Touch points get out of sync with single touch devices; clients stop receiving events"
href="show_bug.cgi?id=69759">Bug 69759</a></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>