1. start gnome-terminal
2. run an application that opens a window from that terminal
3. window wtf happened.
4. figure out that it's underneath the terminal window.
This is seriously driving me nuts.
Relevent upstream bug report:
I thought upstream had already commited a patch to turn this off, but it doesn't
look like it's happened yet.
Let's hold off until it does, and when it does we can push an update.
*** Bug 184235 has been marked as a duplicate of this bug. ***
*** Bug 178389 has been marked as a duplicate of this bug. ***
(In reply to comment #2)
> I thought upstream had already commited a patch to turn this off, but it doesn't
> look like it's happened yet.
> Let's hold off until it does, and when it does we can push an update.
Once the patch arrive, please make the turned off state be the default behavior.
In some application the entire application window is covered by the terminal
window. E.g. try open sabayon.
Seriously, if this "feature" doesn't get fixed soon -- regardless of upstream's
decisions -- I'm switching to KDE or IceWM or something else that is still usable.
Clicking URLs in gnome-terminal opens them in background. Clicking URLs in
Evolution opens them in background. I have never encountered a user interface as
painful to use as this is. A lot of unnecessary extra work is required to
Alt-Tab myself to the correct application.
I've been working on the upstream patch to make this behaviour configurable. A
pre-release version of metacity with the patch applied is available here:
*** Bug 188046 has been marked as a duplicate of this bug. ***
I spend most of my day on the command line. This bug is driving me crazy, and
I've only been using FC5 for about 12 hours. Repeatedly coaxing forward windows
hiding behind my terminal is really hurting my productivity. I'd prefer not to
wait for upstream to fix the problem. Please, make the hurting stop.
Ron: Many thanks for your patched RPM, it has made my desktop usable again.
Sadly, I now live in fear of a yum update bringing back the old behavior.
I'd suggest using Ron's patch in upstream #326159. It's been applied to
upstream cvs head. It'll only make it into the upstream gnome-2-14 cvs branch
if the release team approves the freeze break (which is pending, but possibly
*** Bug 188967 has been marked as a duplicate of this bug. ***
I believe the focus-mode gconf key is in metacity 2.14.1, which is in FC5 by now.
I originally reported this as Bug 178389 against devel. (Closed as duplicate in
comment 4.) The problem still appears to exists in devel with metacity-2.15.0-5.
indeed, this still bites in current FC5+updates as well as rawhide, and this
should really be default rather than force everyone to go fishing for gconf keys.
I don't know about rawhide: maybe someone needs to pull in a newer version from
upstream. But FC5+updates should be OK. The current version of metacity for
FC5 is 2.14.3-1.fc5.1, and that certainly does include my patch. (The Bugzilla
'Fixed in' field is incorrect: the patch was first introduced in
2.14.2-1.fc5.2, but that never made it out of updates-testing.)
The patch turns off the experimental strict-focus approximation behaviour by
default. The only people who need to worry about gconf keys are those who want
it turned on.
This really is supposed to be fixed in both fc5+updates and rawhide. Feel free
to repopen if it isn't.