I originally posted this within
but perhaps is a separate bug? In any case, heres the details:
- am using xfce 4.2.1 RPMs that are about to go into Fedora
- am switching between desktops using <ctl>-<alt>-<left|right>
- using the "focus follows mouse" setting with "raise on click",
"raise on focus", and "new window focus" all set to OFF
- when switching into a new desktop, the focus will frequently be
on the wrong window -- the window directly beneath the mouse
will not have focus as it should -- instead some other window
(often, the last window to have focus within that desktop)
will instead have focus
- moving the mouse out-of and then back-into the desired window
will give it focus
- problem apparently happens with all the applications that I use
including xterm, Firefox, Terminal, Evolution, configuration
windows, etc. and does seem to be related to the applications
themselves -- it seems to be a window manager problem
- problem does not happen every time but it does happen very
frequently -- say, about 1-in-2 or 1-in-3 -- and it does
appear to prefer to focus the last window that had been
active within each desktop
Please let me know if you want any other details.
Sorry, theres a typo in the above bug report!
I meant to say "...and does _NOT_ seem to be related to the applications
Moe has made a very similar report and said that got fixed with the changes
comitted on 03/22
Could you try that version :
If you want to build a rpm out of this file, just do as root
"rpmbuild -ta xfwm4-4.2.1.CVS200503262304.tar.gz"
OK, starting with Kevin's SRPM from:
I modified the spec file to use:
and then rebuilt it (got a clean build--no errors), updated the
RPM, logged out and back in and tested the focus behavior. The
result is no change. I still get the same focus errors and with
about the same frequency as before.
So is there something else I can try?
Ok, I've found the cause of the problem (that was a really stupid bug)
You can grab a copy of the fixed version here :
I've built/installed/tested and am no longer seeing the bug. As far as I can
tell, its fixed -- have not observed a single problem with this new version.
And thank you -- especially for the speedy response !!!