Description of problem: Workspace switcher does not give (or rather, display) focus to the current workspace after unlocking screensaver or clicking on the current workspace Version-Release number of selected component (if applicable): gnome-session-2.8.0-4 metacity-2.8.5-2 How reproducible: Every time Steps to Reproduce: 1. Click on current workspace OR select Lock screen from panel 2. Unlock the screen with password 3. Actual results: The current application in the workspace appears to have lost focus Expected results: Focus should return to the current app Additional info: If you click on the current app in the current workspace in Workspace Switcher, it loses focus. Similarly, if you unlock the PC and look at Workspace Switcher, no workspace is highlighted. If the application is clicked and dragged from the current workspace, Workspace Switcher shows the application moving although it appears to not have focus (the application is not highlighted in Workspace Switcher). This can give the impression that GNOME is not responding, when in fact it is (I got fooled a couple times, until I decided to experiment with it).
Are you still seeing this problem with FC3 final?
Yes. If you unlock the workstation, no workspace appears to have focus and the current windows still has no focus unless you click. If you click on the currently active workspace (even though you can't see that it has focus), it loses focus.
Both of the issues sound like Metacity bugs. In particular: Not getting focus after the lockscreen thing sounds an awful lot like http://bugzilla.gnome.org/show_bug.cgi?id=153220. The other half of the bug sounds like http://bugzilla.gnome.org/show_bug.cgi?id=120100. I'm a little confused why either would show up in FC3 final, though, as both of those fixes were in metacity 2.8.6...
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
Closing per lack of response to previous request for information. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. It has remained in NEEDINFO status for quite a long period of time, asking for confirmation on a more recent (still fully supported) version of Fedora Core. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier.