This is another test -- "+1 +2 +3 -3 -2 -1" on the Stick: http://pastebin.com/f5c8ff5 Works perfectly, no 9p trigger.
Note that button bits are different from TouchPad. This says "1 5 7 5 1 0", whereas TouchPad says "1 17" before it loses sync. Different. WARNING: the TouchPad progression is: +1 Nov 13 00:05:32 localhost kernel: [125574.612295] alps.c: report pad pkt 1 +2 Nov 13 00:05:34 localhost kernel: [125576.222749] alps.c: report pad pkt 17 +3 Nov 13 00:05:36 localhost kernel: [125578.214547] alps.c: looks like a 9p. contents so far: cf 0 0 5f 7f 0 Nov 13 00:05:36 localhost kernel: [125578.215806] alps.c: looks like a 9p. contents so far: cf 0 0 5f 7f 0 Nov 13 00:05:36 localhost kernel: [125578.216762] alps.c: looks like a 9p. contents so far: cf 0 0 5f 7f 0 -3 Nov 13 00:05:42 localhost kernel: [125584.043424] psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost synchronization, throwing 6 bytes away. Lost sync is AFTER I RELEASE the 3. button. -- ALPS DualPoint Touchpad flaky performance https://bugs.launchpad.net/bugs/296610 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
