Found out something new. I compiled the git version of evdev, xf86-input-evdev-2.7.0-20-g5af11b6, and when multitouch isn't enabled, the core state problem is gone. The autoconf script doesn't detect XI22 on Precise because the X.org version is too old, so MT isn't enabled by default.
Once I modified configure.ac to turn MULTITOUCH back on, then the problem was back as well and state is locked to 0x100 after the touchscreen is used.
I've also found that I get far more of the problems Cédric mentions when ginn is running. It seems like what happens is the touchscreen stops generating ButtonPress events, but it still does motion events and state is still locked at 0x100. So the effect is that one is moving the pointer around with the button held down, but never pushing the button. This usually seems like left-click has stopped working. But I imagine the state problem and the resulting "drags with no click" can explain in some strange behavior seen in certain apps.
Found out something new. I compiled the git version of evdev, xf86-input- evdev-2. 7.0-20- g5af11b6, and when multitouch isn't enabled, the core state problem is gone. The autoconf script doesn't detect XI22 on Precise because the X.org version is too old, so MT isn't enabled by default.
Once I modified configure.ac to turn MULTITOUCH back on, then the problem was back as well and state is locked to 0x100 after the touchscreen is used.
I've also found that I get far more of the problems Cédric mentions when ginn is running. It seems like what happens is the touchscreen stops generating ButtonPress events, but it still does motion events and state is still locked at 0x100. So the effect is that one is moving the pointer around with the button held down, but never pushing the button. This usually seems like left-click has stopped working. But I imagine the state problem and the resulting "drags with no click" can explain in some strange behavior seen in certain apps.