| Summary: | Numlock is stuck on | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bruno Wolff III <bruno> |
| Component: | xorg-x11 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | bruno, bugzilla-redhat, clydekunkel7734, mrmazda, tomh0665 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-03-03 07:23:38 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Bruno Wolff III
2012-02-20 22:50:54 UTC
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. |