Bug 232942 - numlock/capslock/scrolllock LEDs don't work in 2.6.20 kernel
numlock/capslock/scrolllock LEDs don't work in 2.6.20 kernel
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Pete Zaitcev
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2007-03-19 11:46 EDT by David Mueller
Modified: 2008-05-06 15:22 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 15:22:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Linux Kernel 7968 None None None Never

  None (edit)
Description David Mueller 2007-03-19 11:46:11 EDT
Description of problem:

With the most recent kernel update (2.6.20-1.2300.fc5smp), the numlock and
capslock lights on my keyboard don't work.  The keys do work, just the lights
don't appear.  Keyboard is a Microsoft Comfort Curve 2000, connected via USB to
a ThinkPad X60.

The capslock light on the laptop itself does work when I press either the
capslock key on either the built-in or external keyboard, as does numlock when I
use the laptop's built in keyboard.

If I reboot to the previous kernel (2.6.19-1.2288.2.4.fc5smp) the lights work

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

$ uname -r

Steps to Reproduce:
1. Boot 2.6.20-1.2300.fc5smp
2. Press numlock and capslock
Actual results:

Numlock, capslock, scrollock lights on keyboard don't illuminate.  Type in a
text editor to confirm the keys do work.

Expected results:

Numlock, capslock, scrollock lights on keyboard illuminate.

Additional info:

It looks like this bug has been reported upstream, but there doesn't appear to
have been any activity there for almost a month:


It looks like Ubuntu users are seeing the same problem with 2.6.20 kernels:

Comment 1 Bug Zapper 2008-04-04 02:35:34 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 2 Bug Zapper 2008-05-06 15:22:55 EDT
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.