I was running Vinagre (gtk vnc client) which appears to do some kind of input stealing when its vnc widget has focus. I suspended my laptop and on resume keyboard input was working, the mouse pointer moved (and pointers updated in the right places, e.g. window borders showed a resize pointer), but X apps were not able to see pointer motion events or mouse buttons. restarting hal, rmmoding, changing VTs, etc. were not able to restore normal behaviour. xinput test was seeing motion and button events. locking the screen with gnome screensaver and then unlocking, returned things to normal. Presumably X was still under the impression that something was grabbing mouse events even though I had killed vinagre from a console (but before killing it, things had already gone wrong).
This is completely reproducible in current Ubuntu karmic: 1. Run vinagre, connect to a remote host. maximise the window 2. Ensure the mouse is within the vnc widget (ie events are being sent to the remote host) 3. Close your laptop so it suspends 4. Open your laptop 5. Marvel at your inability to send useful events to things 6. Drop to a console, killall vinagre, you can now send keyboard events 7. lock display, unlock. all is now normal.
[21:22] < bryce> Ng, mind upping the priority on your fdo bug 22186 to high please, so it matches the priority in lp?
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.