Comment 25 for bug 1015183

Hello,

Thanks Martin for your PPA and the precise packages; unfortunately, I run amd64 :-/

I first applied only #19 patch (yes, it did require some adjustments) to the latest precise X.org packages (1.11.4-0ubuntu10.3): behavior remains the same (at least as far as Compiz plugins are concerned: "Expo" triggers the issue systematically, "Shift Switcher" one time out of two).

Then I saw Martin's comment and applied patches #11 and #19: behavior remains the same (as far as Compiz plugins...) AND windows moving (clicking-holding-dragging) is lost right from the start.

I think we can conclude that #11 triggers the "windows moving (clicking-holding-dragging) is lost" issue (since I also bumped into it #17)

Now, I'm wondering whether Compiz might have some problem on its own. Example given: I loose single/double click as soon as I launch the "Expo" plugin and select (double-click on) a viewport. After, no amount of single/double-clicking does anything (on desktop icons, windows minimize/maximize/close buttons, panel applets, etc.). BUT, single/double-clicking still work in Compiz plugin (if I launch the "Expo" or "Shift Switcher", single/double-clicking works).

I also gave #19 patch (alone) a try without launching Compiz (use metacity alone instead) or multi-touch (ginn) stuff. Before, even in that (no-compiz/no-ginn) scenario, single/double-clicking got lost rather rapidly. Here, I've been clicking and double-clicking around and using applications for several minutes without any problem. As soon as I launch ginn again, I start to have some problems with the applets icons (most of the time, they don't react to single click, though they sometime - rarely - still do). Other single/double-clicking still works.
Launching Compiz alone (without ginn), and all problems are back.

Conclusion using patch #19, without patch #11 (cf. "windows moving (clicking-holding-dragging) is lost" issue), without Compiz (cf. "single/double-clicking is lost" issue) and without ginn (cf. "applets react only whimsically to single-click" issue), single/double-clicking at least seems to work reliably enough to allow the touchscreen to be used (before, it was a "no go"), even if sometime, one must (single) click two time on an icon for the expected behavior to happen.

About that "sometime, one must (single) click two time on an icon for the expected behavior to happen": I can reproduce the behavior systematically by: 1. clicking on a network-manager icon (menu opens), 2. clicking on the desktop to close the menu (menu closes), 3. clicking on a network-manager icon again (menu does not open; instead, a selection rectangle is drawn), 4. clicking on a network-manager icon again (this time, menu opens again)

Let me know if I can help any further.