RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 631278 - [RHEL6] numlock key does not work with all configurations
Summary: [RHEL6] numlock key does not work with all configurations
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: control-center
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Control Center Maintainer
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-07 18:02 UTC by Jeff Burke
Modified: 2010-09-08 17:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-08 17:29:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jeff Burke 2010-09-07 18:02:26 UTC 
Description of problem:
 My desktop is currently using the RC tree. I noticed this between snap 11 or snap 12. The numlock light goes on and off when I hit the numlock key but when it is on. I can't use and numlock keys.

Version-Release number of selected component (if applicable):


How reproducible:
 Always

Steps to Reproduce:
1.
2.
3.
  
Actual results:
 Nothing happens

Expected results:
 When numlock is on, It should work

Additional info:
 This has been seen on several different configurations.
Comment 2 Cameron Meadors 2010-09-07 19:13:51 UTC 
I also see this problem.  I have a Lenovo T500. If I turn on NumLock with FN-ScrLK key, the NumLock indicator lights up, but I can not type numbers using the number pad.  In fact I get nothing except for the comma key with types a comma sometimes.  In gnome terminal I even get a menu pop up when hitting some of the number pad keys.  Same thing happens with my usb Goldtouch (KeyOvation) keyboard.  I have snap13 install currently.  I will update to RC1 and retest.
Comment 3 Vladimir Benes 2010-09-07 19:55:34 UTC 
btw: is the accessibility mouse by keyboard disabled? I know a stupid question.. :)
Comment 4 Jeff Burke 2010-09-07 20:23:04 UTC 
Not a stupid question at all. On the Menu if I go to System -> Assistive Technologies Preference then click on Keyboard Accessibility -> Mouse Keys tab, Pointer can be controlled using the keypad is checked.

Do you think that could be causing my issue? fwiw I have never been in this menu before. If that is the issue perhaps something changed to enable it?
Comment 5 Vladimir Benes 2010-09-07 20:31:51 UTC 
if this is checked, you can then control your cursor by pressing num keys.. is your cursor moving while you press num keys? if yes, disable it and voila you can write numbers again
Comment 6 Cameron Meadors 2010-09-07 21:11:17 UTC 
That option was on for me, but this is a home directory that has been carried over from other installs.  With a new user, the option is not checked.  So the default appears to not have cursor keys move the mouse.

Either way, disabling the option allows me to type numbers with the keypad.  Enabling the option lets me control the cursor with the keypad.  I guess that makes this bug a NOTABUG candidate.
Comment 7 Thomas Woerner 2010-09-08 09:36:27 UTC 
Jeff: Is this a problem on text consoles or on your desktop? Which desktop environment are you using BTW?
Comment 8 Jeff Burke 2010-09-08 12:53:29 UTC 
Reply Comment 5
 Q: If this is checked, you can then control your cursor by pressing num keys.
 A: No it does not seem to control my cursor.

 Removing the check box from "Pointer can be controlled using the keypad" I have my numlock selections back. Thank you!

Reply Comment 6
 The strange thing about this is. This system was built from scratch several updates ago. I have new home dir local so nothing was carried over. My desktop was fine numlock was working up until a recent update snap 11 or snap 12 not really sure.

  I agree with Cameron this bug a NOTABUG candidate. 

Reply Comment 7
 Q: Is this a problem on text consoles or on your desktop?
 A: Both, It is a problem with in text(tty2) and in any application in gnome.

 Q: Which desktop environment are you using BTW?
 A: gnome.
Comment 9 Thomas Woerner 2010-09-08 13:44:56 UTC 
This is expected behaviour for GNOME, but setting "Pointer can be controlled using the keypad" should not affect text consoles. 

Therefore I am reassigning this to control-center for now.
Comment 10 Ray Strode [halfline] 2010-09-08 17:29:30 UTC 
I'm going to assume if you toggle the numlock key twice while at a text console (1 time to turn off mouse keys, a second time to turn on numlock) then things start behaving, so I don't think that's actually a bug.  Arguably X, should save and restore numlock state when switching VTs, but that's pretty debatable.

I'd say NOTABUG, if there isn't too much disagreement with me.

There are a couple of questions up in the air:

1) How did mouse keys get enabled in the first place?
2) Why doesn't mouse keys work on this system?

Both are reasonable questions that may be real bugs.  Jeff, if you'd like like to pursue either or both those issues, feel free to clone this bug and we can investigate from there.
Note You need to log in before you can comment on or make changes to this bug.