Red Hat Bugzilla – Bug 108674
The gnome panel can no longer get mouse focus.
Last modified: 2007-11-30 17:10:32 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031027
Description of problem:
After upgrading to metacity-2.6.3-1 from rawhide applets in the panel
no longer get keyboard focus in the anticipated way when using Focus Follows
Mouse. Everything works fine if using Click To Focus.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Log in using a gnome session.
2.Add a panel applet which requires keyboard input.
3.Set the window mode to "Select windows when the mouse moves over them"
4.Move the mouse over the panel applet, and attempt to enter text.
Actual Results: The mouse cursor changes to indicate it is over a text field,
but the text cursor does not appear, even when the test field is clicked.
The window that previously had focus still has focus, and key presses do not
appear in the applet, but are instead sent to the window that previous had focus.
Expected Results: Focus should switch to the panel applet, a text cursor should
appear, and keypresses should appear in the text box.
Additional info: Two applets that are affected are Dictionary Lookup and Command
I can verify this on two additional systems.
Looking at the changelog between 2.6.2 and 2.6.3, it looks like this
problem may have been introduced by the final commit made on
2003-10-25 by Havoc Pennington:
2003-10-25 Havoc Pennington <email@example.com>
* src/window.c (meta_window_notify_focus): if a window is focused
which is not either a dock or a transient in the same group as
dock, shuffle all dock/desktop windows to the end of the MRU list
so they won't annoyingly get focus all the time. #123816
*** Bug 109435 has been marked as a duplicate of this bug. ***
This is the same as the infamous bug 115072 on bugzilla.gnome.org.
This has since been fixed, so this bug should probably be closed as
The bug appears to be fixed in Fedora Core 2 which ships with metacity
2.8.1. It seems a shame that even though the bug was fixed, an update
was not issued for Fedora Core 1.
I agree, but since there isn't one:
If anyone needs an update (unofficial, obviously) that works for
Fedora 1, you can download the one I created at
In the spirit of community contribution that is supposed to be
inherant in Fedora, it seems to make sense for the community to
provide fixes for problems like this, but there is no obvious
mechanism for letting the community at large know about updates that
RedHat are unwilling or unable to fix internally.