GNOME Bugzilla – Bug 676310
Key events going to the wrong window
Last modified: 2014-01-12 23:43:56 UTC
(This could be mutter but, I'm not sure) It happens *sometimes* that key events are dispatched to the wrong window. My steps are: 1) have xchat-gnome on workspace 1 2) have firefox in workspace 2 3) open a link in xchat-gnome, a notification is shown telling that firefox has loaded the page. 4) click that notification, read the page, hit ctr-w to close the firefox tab... nothing happens 5) switch back to xchat-gnome and see that it closed your channel The ctr-w event went to xchat-gnome even though that the screen was displaying firefox window. Note that I can't reproduce that every time, maybe something is slightly different in the steps to reproduce reliable... But I often realize much later that I left some channels.
(In reply to comment #0) > (This could be mutter but, I'm not sure) > > It happens *sometimes* that key events are dispatched to the wrong window. My > steps are: > > 1) have xchat-gnome on workspace 1 > 2) have firefox in workspace 2 > 3) open a link in xchat-gnome, a notification is shown telling that firefox has > loaded the page. > 4) click that notification, read the page, hit ctr-w to close the firefox > tab... nothing happens > 5) switch back to xchat-gnome and see that it closed your channel > > The ctr-w event went to xchat-gnome even though that the screen was displaying > firefox window. > > Note that I can't reproduce that every time, maybe something is slightly > different in the steps to reproduce reliable... But I often realize much later > that I left some channels. What's happening is that Firefox isn't actually focused. Also I do the exact same thing you do and it annoys me beyond belief. I suggest setting up an alias for "/i" that's "/me kicks XChat".
I'm also experiencing this bug from times to times.
Let's make this blocker. Sending events to the right windows is the least we can ask from a WM.
(In reply to comment #2) > I'm also experiencing this bug from times to times. How? Is it the situation I described above, which is after clicking on "X is ready" notifications? As far as I'm aware, that was fixed long ago. Next time it happens, look at if the window is focused or not.
(In reply to comment #3) > Let's make this blocker. Sending events to the right windows is the least we > can ask from a WM. The wm is not involved in sending key events. The X server does that.
This was fixed at some point.