Comment 25 for bug 581312

So from looking at http://launchpadlibrarian.net/48618312/UdevDb.txt, there are several input devices which look a bit perculiar and could emit this:

P: /devices/pci0000:00/0000:00:1d.1/usb7/7-2/7-2:1.1/input/input6
E: NAME="N-Trig Pen"
E: ID_INPUT_TABLET=1

This is recognized as a mouse and tablet.

P: /devices/pci0000:00/0000:00:1d.1/usb7/7-2/7-2:1.1/input/input7
E: NAME="N-Trig MultiTouch"
E: ID_INPUT_TOUCHSCREEN=1

This is likely the touchscreen.

P: /devices/pci0000:00/0000:00:1d.1/usb7/7-2/7-2:1.1/input/input8
E: NAME="N-Trig Touchscreen"
E: ID_INPUT_TOUCHSCREEN=1

Hm, why is it detected as two different devices? Jeremy, any idea?

P: /devices/virtual/input/input14
E: NAME="Promethean Limited ACTIVboard"
E: ID_INPUT_TABLET=1
E: ID_INPUT.tags=promethean

I have no idea what that one is, it acts as another mouse.

I don't see any input product name which sounds like "accelerometer", maybe this hides behind the promethean thing or the mysterious double N-Trig touchscreen? Also, it seems weird to me that an accelerometer sends EV_KEY events, I'd rather expect EV_ABS or at least EV_REL, i. e. movements and axis posititions, not key events.

Aside from the ones I quoted above, you also have a range of audio devices which provide input devices for jack sensing. Perhaps one of those goes crazy, too.

Mark, what would help here is to find out which input devices actually spits out those events. For this, you can run

  sudo /lib/udev/keymap -i input/eventX

with X from 0 to 16 on your system, then wiggle the laptop as you did before, and check which one generates those events.

Unfortunately it's likely that the assignment of event device numbers changes across reboots, so if you rebooted your laptop since then, you can only try (or check lsinput for the ones from above). Once you found the correct X, please copy&paste the output of

  udevadm info --attribute-walk --name=input/eventX

Thanks!