Description of problem: I updated to metacity 2.15.34 yesterday and it seems having major issues with my laptop. I have a touchpad which is somewhat screwy and generates extra events sometimes. I know that it's broken, but until today it only required a companion event. E.g. if middle button got stuck, I middle-button again, and all is fine. But now, it's very, very hard to convince Metacity to clear a paired event. I still do not have a failure-proof way to do it. Version-Release number of selected component (if applicable): metacity-2.15.34-1.fc6 How reproducible: Not easily, you have to have hardware which unbalances events, e.g. Middle down, Middle down, Middle up. Steps to Reproduce: 1. On a certain hardware setup, work normally with a couple of terminals. Eventually it has to get stuck with the title bar changing to focus, but actual focus not getting to the application. Actual results: Unable to restore keyboard focus. Expected results: Keyboard input restoring when erroneous mouse events are cleared. Additional info: I'm afraid this is not something easy to reproduce elsewhere. So I'd like someone to look at diffs between 2.15.21 and 2.15.34. The things to look at is how Metacity compares events, and if anything was changed. But most especially if someone decided to keep a counter instead of a flag for mouse buttons.
I see that I probably was wrong about counters. The right recovery involves sending the second event where Metacity can see it. In other words, if your middle button got stuck, middle button into the title bar, and not anywhere else into the application.
This is a duplicate of bug 204519.
nyorirooon.... *** This bug has been marked as a duplicate of 204519 ***