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 118491 - Keyboard focus lost after application is started.
Keyboard focus lost after application is started.
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: panel
unspecified
Other Solaris
: Urgent critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
AP1
: 118252 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-07-28 16:21 UTC by david.hawthorne
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Proposed patch (1.14 KB, patch)
2003-08-05 14:36 UTC, padraig.obriain 		none Details | Review

Description david.hawthorne 2003-07-28 16:21:57 UTC 
Using gnome-2.4 nightly build from 22 July 2003.

.logged in as root or normal user

Whilst trying to navigate gnome without the mouse, using only keyboard
shortcuts, I got locked in the top panel and could not focus any other
active windows.

reproduce:

- hit alt-f1 to bring up top panel applications menu
- use keyboard to launch app like gedit
- hit alt-tab and try to select newly opened window

.alt-tab does nothing and all that you can do is cycle through the
selections in the top panel. This is pretty critical for users who rely on
navigating solely with the keyboard. The only escape I found was to click
out of top panel with the mouse.
Comment 1 david.hawthorne 2003-07-29 09:54:47 UTC 
this bug is similar to the one below:

http://bugzilla.gnome.org/show_bug.cgi?id=114480
Comment 2 padraig.obriain 2003-07-30 14:52:32 UTC 
With build from July 29th I see the following:

- Hit Alt+F1 to bring up top panel applications menu.
- use keyboard to laucnh an app, say Text Editor

Text Editor window shows focus but will not accept keyboard input.
Must use mouse to recover.
Comment 3 Calum Benson 2003-07-31 20:40:12 UTC 
Marking AP1 to reflect a11y team's assessment of accessibility impact.
Comment 4 padraig.obriain 2003-08-05 10:10:04 UTC 
It looks like XUngrabKeyboard is not being called when we launch an
application. It is called when we click with the mouse in the
application.

I think this explains what is happening. Now to understand why ...
Comment 5 padraig.obriain 2003-08-05 14:35:49 UTC 
I have compared the code in panel-menu-bar.c with what happens when
F10 is used to activate menubar in an application which explains the
patch I am about to attach.
Comment 6 padraig.obriain 2003-08-05 14:36:21 UTC 
Created attachment 18926 [details] [review]
Proposed patch
Comment 7 Calum Benson 2003-08-07 16:16:06 UTC 
Apologies for spam... marking as GNOMEVER2.3 so it appears on the official GNOME
bug list :)
Comment 8 padraig.obriain 2003-08-08 16:39:12 UTC 
*** Bug 118252 has been marked as a duplicate of this bug. ***
Comment 9 Mark McLoughlin 2003-08-11 12:14:56 UTC 
The patch looks great Padraig, thanks :-)

I knew that code was dodgy when I wrote it ... :/
Comment 10 padraig.obriain 2003-08-11 12:27:38 UTC 
Patch committed to CVS HEAD.