Hide Forgot
Created attachment 547487 [details] xev output Description of problem: I use XFCE and I selected "focus follows mouse" with the shortest possible delay. Quite often when I move the mouse cursor from one window over a second window to a third window, the focus is given to the second window instead of the third (where the mouse cursor ends up). I'm not sure in which component the bug is, so I assigned it to a component that is involved. Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.11.2-3.fc16.x86_64 xfce4-session-4.8.2-1.fc16.x86_64 How reproducible: It happens often but by no means all the time. Steps to Reproduce: 1.create three windows from three applications 2.move the mouse cursor quickly from window 1 over window 2 to window 3 3. Actual results: focus sticks to second window Expected results: focus on third window Additional info: Attached is xev output. I moved the mouse cursor back and forth from firefox over Terminal (from which I started xev and which therefore contained the xev output) to xev. I stopped (interrupted xev) when the focus was given to Terminal while the mouse cursor was inside the xev window. Note that normally an EnterNotify event is followed by a FocusIn event (usually with a bunch of MotionNotify events inbetween), but the output ends with just the EnterNotify and MotionNotify events.
If you adjust the delay up and move the mouse more slowly does it change anything? Or does the same thing? Would you be willing to file this upstream? Or would you prefer I do so for you?
I remember getting really frustrated because of this bug because it happened a lot, but now I can't reproduce it anymore. When I reported this I had xfwm4-4.8.2-1.fc16.x86_64, but now I have xfwm4-4.8.3-1.fc16.x86_64. It looks like something has changed for the better here. As far as I am concerned, this bug can be closed. I can always reopen and provide the asked for details when it happens again.
excellent. ;) Please do reopen or file a new one if you see this happen again.
Reopening since it is still actually a problem. For quite a while now I've been bugged by this problem again. I don't know what the significant changes was, or perhaps I was just lucky when I replied back in February. In any case, I'm now using a fully up to date Fedora 17 (fresh install from Live CD, but with old /home), still with XFCE. I am now running this with a slightly higher delay (see comment 1), and I have yet to experience the problem, but the problem doesn't happen all the time with a zero delay either, so it is too early to tell whether the delay helps. I am getting the impression that the problem is worse if programs have to be paged in, i.e. when a program can't respond immediately to a focus event. But this is pure speculation and may well be a red herring.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.