After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 96393 - Desktop switching loses keyboard focus with focus-follows-mouse
Desktop switching loses keyboard focus with focus-follows-mouse
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: general
unspecified
Other other
: Normal minor
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on: 90382
Blocks:
 
 
Reported: 2002-10-21 09:51 UTC by Ilkka Tuohela
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description Ilkka Tuohela 2002-10-21 09:51:40 UTC 
When switching desktop with shortcut keys and focus-follows-mouse, it
often happens that no window gets keyboard focus. A window seems to be
selected by decoration but keyboard input goes nowherere.

I cant' reliably reproduce this, it happens maybe every fifht change of
desktop... Anyway, when it happens you can always get focus
by cycling through the windows. Keyboard focus doesn't work if you 
select new window with mouse or from task list. Going to another desktop
and coming back helps as well, but only when you do it with keyboard,
there seems to be no way to get focus to any window by selecting the 
window with mouse.

This is not necessarily metacity's fault, I've seen it with sawfish gnome2
version as well, just more often with metacity.
Comment 1 Havoc Pennington 2003-02-25 20:26:49 UTC 
I don't think most people are seeing this, so it's a bit hard to 
know where we stand on it. (Are you perhaps not running 
nautilus? that might explain why you see it but not others)
Comment 2 Ilkka Tuohela 2003-02-26 10:15:20 UTC 
I haven't seen this myself for a while, right now I'm using gnome 2.2
from debian and this _never_ happens there.
Comment 3 Havoc Pennington 2003-02-26 16:08:43 UTC 
OK, assuming it's gone away then, at least for now.