@Charles: Yes. PAE extension isn't harmful, you can use it just as well. It only allows more than 4GB RAM on a 32bit machine.
@Sebastian: I sort of debugged the problem, it's definitely the driver, not X or WM. Try following: Exit X (so your /dev/input devices are not grabbed) and run (from package input-utils) as root: # input-events -t 120 X & input-events -t 120 Y (X = evdev number of TouchPad, Y = Stick; find these using lsinput) This is how it should work: 1) push PadLeft -> EV_KEY BTN_LEFT pressed 2) push StickLeft -> EV_KEY BTN_LEFT pressed 5) release StickLeft -> EV_KEY BTN_LEFT released 4) release PadLeft -> EV_KEY BTN_LEFT released Now ALPS has a definite bug: 1) push PadLeft -> EV_KEY BTN_LEFT pressed 2) push StickLeft -> EV_KEY BTN_LEFT pressed 4) release StickLeft -> NO event! - now you can click StickLeft like mad, no events! 5) release PadLeft -> EV_KEY BTN_LEFT released At this point, PadLeft has correct state, but StickLeft is incorrectly "pressed" for the input subsystem. Until you click it or generate any other Stick event. You can switch 4) and 5) to break PadLeft state instead. -- 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
