Hide Forgot
Description of problem: Something on the order of a week ago the numlock setting on my rawhide and f17 machines stuck on. Hitting the numlock key does not change the setting. I am not sure exactly which package to file this against, but X seemed a good starting point. I am using the gnome desktop in fallback mode on all of these machines. I have both usb and ps/2 keyboards. I have both i686 and x86_64 machines. Version-Release number of selected component (if applicable): xorg-x11-server-common-1.11.99.901-6.20120124.fc17 How reproducible: 100% Steps to Reproduce: 1.Note the numlock light is lit and stays lit when the numlock key is hit. 2. 3. Actual results: Expected results: Additional info:
I hope this is part of some configurable new kernel feature that will enable those of us who want NUM permanently on and/or permanently matching the BIOS setting to have it.
Just posted to "test" list: I installed F17 (F17 Desktop Live CD) and Rawhide (F16 Desktop Live CD, upgraded to Rawhide) on Sunday on the same netbook. In F17, logging in to GNOME, numlock's on and cannot be turned off in Terminal and numlock's on and can be turned off on a virtual console while logged in to GNOME. After logging out of GNOME, numlock's off when logging in to a virtual console. In Rawhide, no numlock problem.
This is a bug in gnome-settings-daemon which has been fixed in upstream git. Should be in the GNOME beta release of this week. http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=ebca1ce1287679c5cb470804abfcc8de3c2d740c
To correct what I said in #2: I installed RC4 and numlock was off. But I pressed CapsLock and numlock came on and stayed on. I tried in in Rawhide and the same thing's happened. So my "In Rawhide, no numlock problem." in #2 wasn't quite right... @Olav: Thanks.
This seems to be fixed now.