<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c5">Comment # 5</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 <a class="email" href="mailto:neil@linux.intel.com" title="Neil Roberts <neil@linux.intel.com>"> Neil Roberts</a> <pre>I think this bug is caused by the patch in <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [bug] wl_touch::down event has wrong coordinates" href="show_bug.cgi?id=51909">bug 51909</a>. As you can see from the last section of Rusty's evtest log, it is getting multiple touch up events in-between SYN events. After that patch the touch up events are only flushed once the SYN event is received. However the evdev_device struct only keeps track of a single pending EVDEV_ABSOLUTE_MT_UP event so the earlier touch up event gets overridden by the second one and so it never gets emitted. I can reliably replicate the bug by removing my fingers at the same time. If I revert the patch from that bug it seems to fix the problem. Maybe we could fix this bug without breaking <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [bug] wl_touch::down event has wrong coordinates" href="show_bug.cgi?id=51909">bug 51909</a> by setting the pending sync flag whenever we get a slot event as well?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>