For those of us who hit this issue and are proficient programmers (sarvatt, sforshee, laney, hint hint :), I suggest adding some debug statements inside the src/eventcomm.c touch handling functions to see exactly what is going on. The patch that RAOF added for this bug resets the touch state when the device is re-enabled, which I think happens on resume, so something is likely going wrong after that. Logging touch count changes would be a good first start, since the touch count determines whether the left or right clicks are emitted, and whether the cursor is moved or two-touch scrolling occurs.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 on MacBookAir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/968845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
