[PATCH xf86-input-evdev] Allow multitouch support to be disabled

[Peter Hutterer]

On Fri, Oct 19, 2012 at 08:11:05AM +0200, Thierry Reding wrote:
> On Fri, Oct 19, 2012 at 04:12:10PM +1000, Peter Hutterer wrote:
> > On Fri, Oct 19, 2012 at 07:50:04AM +0200, Thierry Reding wrote:
> > > On Fri, Oct 19, 2012 at 08:44:00AM +1000, Peter Hutterer wrote:
> > > > On Thu, Oct 18, 2012 at 12:54:35PM +0200, Thierry Reding wrote:
> > > > > On Thu, Oct 18, 2012 at 08:36:30PM +1000, Peter Hutterer wrote:
> > > > > > On 18/10/12 20:32 , Thierry Reding wrote:
> > > > > > >Instead of always automatically including multitouch support if the
> > > > > > >mtdev library is installed, the new --disable-multitouch option can
> > > > > > >be used to forcefully disable multitouch support in the driver.
> > > > > > 
> > > > > > uhm. seems a bit like the proverbial sledgehammer. what's the reason
> > > > > > for this?
> > > > > 
> > > > > It turns out that the stuck key issue that I've seen with the OSK is
> > > > > related to multitouch. If I apply this patch to the xf86-input-evdev
> > > > > driver and rebuild with --disable-multitouch the issue is gone.
> > > > 
> > > > well, yes. but the real question in this case is whether the bug is in the
> > > > driver (don't think so, given the previous logs), in the server, or in the
> > > > client.
> > > 
> > > Early log output seems to indicate that indeed the button press events
> > > are generated by the server but for some reason no release event is
> > > emitted afterwards.
> > > 
> > > I've trimmed down the test case to a very rudimentary Gtk+ client that
> > > captures only the button-press and button-release events of a top-level
> > > window and can reproduce with that as well. That has the further
> > > advantage that output from xscope is much reduced since no redrawing
> > > takes place and the only data exchanged is the input events (and the
> > > usual housekeeping).
> > > 
> > > Unfortunately some other more urgent stuff came up so I had to postpone
> > > further analysis. I hope I can get more time later today or hopefully
> > > next week to get you a full xscope log along with the test program.
> > 
> > have you looked at Thomas Jaeger's test app? can you reproduce with that
> > one? it's likely the same bug and it's a simpler start than Gtk :)
> 
> Right, I could use that. I had actually been thinking about writing a
> similar test program to exclude Gtk+ but it seems exactly like what I
> need. Thanks for bringing that back to my mind.

having had a chance to test it now I can see the mismatched events. This is
certainly a bug in the server and Thomas' test case exposes it very well.
I'll try to debug this on Monday.

Cheers,
   Peter