After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 676310 - Key events going to the wrong window
Key events going to the wrong window
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Urgent blocker
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-05-18 11:47 UTC by Xavier Claessens
Modified: 2014-01-12 23:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Xavier Claessens 2012-05-18 11:47:08 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.
Comment 1 Jasper St. Pierre (not reading bugmail) 2012-05-18 17:28:52 UTC
(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".
Comment 2 Guillaume Desmottes 2012-11-06 14:46:09 UTC
I'm also experiencing this bug from times to times.
Comment 3 Xavier Claessens 2012-11-06 14:47:53 UTC
Let's make this blocker. Sending events to the right windows is the least we can ask from a WM.
Comment 4 Jasper St. Pierre (not reading bugmail) 2012-11-06 16:07:53 UTC
(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.
Comment 5 Matthias Clasen 2012-11-07 00:38:29 UTC
(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.
Comment 6 Jasper St. Pierre (not reading bugmail) 2014-01-12 23:43:56 UTC
This was fixed at some point.