281626 - On some X servers keyboard does not work if numlock is active

Status: RESOLVED WONTFIX

(Core :: Widget: Gtk, defect)

Description

[Bob Vickers]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

This problem has been reported against the Solaris and Tru64 versions (bugs
140050 and 160695) but also applies to Linux. Although the workround is trivial
(just press numlock) the problem is annoying because most users who encounter it
do not realise what is happening and just assume that Mozilla is completely
broken and unusable.

The problem manifests itself when Mozilla is displaying remotely on certain X
servers, for example NCD Exploras and Tru64 workstations. As soon as the numlock
key is pressed Mozilla becomes unusable because key presses in the URL toolbar
are ignored.

Fortunately you don't need unusual equipment to reproduce the problem; just type
  xmodmap -e 'add mod4 = Num_Lock'
then hit the numlock key.


Reproducible: Always

Steps to Reproduce:
1. xmodmap -e 'add mod4 = Num_Lock'
2. hit the numlock key
3. try typing in the Mozilla URL box.

Actual Results:  
Key presses are neither echoed nor responded to

Expected Results:  
Echoed the key presses and responded to my desires

Comment 1

[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 2

[Bob Vickers]

Problem is still present in Firefox 1.5 beta 1.

Comment 3

[Mats Palmgren (inactive)]

Does this bug occur in a recent trunk build?
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

Comment 4

[Bob Vickers]

Yes, the bug still occurs in both Firefox 2.0.0.3 and Minefield 3.0a5pre

Comment 5

[Martin Stránský [:stransky] (ni? me)]

We're not going to fix that.