This issue was discussed on irc the other day, and I'm going to attempt to summarize the findings here.
The MBA has a magnet near the camera, and as the lid is closed this magnet induces touchpad activity. The resulting stream of input events from the driver show the start of a multitouch sequence that never completes. xf86-input-synaptics is left in a bad state, waiting for the completion of the multitouch sequence. There's also a possibility that the events will result in unintended actions being performed on the destkop (I've noticed from time to time that the dash is exposed after resume when it wasn't at the time the lid was closed, which may be evidence of this). The proposed fix is for xf86-input-synaptics to listen for the input event that indicates the lid has been closed and to stop listening to internal input devices at that time. There's still a chance that events caused by the magnet will be received before the lid-close event when the lid is closed very quickly, but that seems to be unavoidable. xf86-input-synaptics may also need to reset its internal state after the lid is opened to ensure that it's not left waiting for events it's never going to receive. Chase, does this correspond to your takeaway from the discussion? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/968845/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
