Bug 171361
Summary: | run numlockx before gdm | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Mahowald <jpmahowald> |
Component: | numlockx | Assignee: | John Mahowald <jpmahowald> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | extras-qa, triage |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | bzcl34nup | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-07 00:15:43 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John Mahowald
2005-10-21 05:41:48 UTC
Submitting a vote in favor of this change. (Unless GDM becomes properly trained to obey the BIOS setting w.r.t. NumLock state.) Upon booting systems with USB keyboards the NumLock LED tells a lie at the GDM login greeter. All users here like to use the numeric keypad as a numeric keypad and find it doubly irritating when the NumLock state is off when the LED says its on. I don't know how numlockx works but I'm not sure if simply running it before gdm will do the trick. In my experience, GDM is determined enough to turn numlock off even if it has already been turned on. Here's the trick I've been using to turn numlock on at GDM: 1. Remove /etc/X11/xinit/xinitrc.d/numlockx.sh 2. In /etc/X11/xdm/Xsetup_0 add a line "/usr/bin/numlockx on". Could the numlockx RPM post-install script be changed to do the same? Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. This bug has been in NEEDINFO for more than 30 days since feedback was first requested. As a result we are closing it. If you can reproduce this bug in the future against a maintained Fedora version please feel free to reopen it against that version. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp |