188268 - no keyboard input for X apps after switching to/from Mozilla with Gnome keyboard shortcuts, sometimes

Status: RESOLVED EXPIRED

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[Dustin Mitchell]

User-Agent:       Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.3b) Gecko/20030108
Build Identifier: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.3b) Gecko/20030108

Using the keyboard shortcuts I have mapped in Gnome to flip from one "destkop"
to another (F1-F4; I've tried with Mozilla in all different desktops),
occasionally after flipping to a desktop on which Mozilla is maximized and then
back, I can't type in an xterm, nor in any other X app.  This seems to occur
more often when I flip quickly (so Mozilla doesn't have a chance to completely
redraw before the window manager gets the shortcut to switch away from Mozilla)
but even then it's not consistent.

This doesn't seem to happen if I use the mouse to select the desktops on the
little desktop navigator applet.  But that may be because I don't mouse fast
enough to trigger it.

Once I've lost the keyboard, the F1-4 keys still work, but I have to press them
twice.  I can regain keyboard focus by doing one of two things: Pressing the F
key for Mozilla's desktop *three* times (it flips to Mozilla after the second);
or flipping to a different virtual terminal and back (e.g., alt-ctl-f1, alt-ctl-f7).

Reproducible: Sometimes

Steps to Reproduce:
1. Set up an Moz on desktop 1 and an xterm on desktop 2.
2. Flip from desktop 2 to 1 and back again quickly, using the keyboard shortcuts

Actual Results:  
Nothing accepts keyboard input

Expected Results:  
Everything accepts keyboard input

I'm using RH 8.1; modern theme.  I would love to test this further, but I'm
really just shootin' in the dark here.  If you have things you'd like me to try
out, let me know.

Comment 1

[Aaron Leventhal]

-> Akkana

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.