4

I often notice that the NumLock LED is off although NumLock mode is on actually and the numeric keypad works as it is meant to when NumLock is on. Pressing NumLock twice (to turn it off and on again) lights the LED up. The effect only takes place on Ubuntu (16.04), it doesn't take place when running Windows XP, Windows 7 or Xubuntu (15.10) on the same machine.

This is tolerable but a little bit annoying and I'd like to fix this if possible. Does anybody here happen to know the reason behind this quirk and ways to cure it?

Ivan
  • 57,065

1 Answers1

3

This is a known little bug -> Num LED state does not correspond with actual state after boot.
It happens when starting to type too early after booting the computer. It also happens when opening an application with root privileges too early. If you wait about one or two minutes, it works flawlessly. As it is one of them 'not so important' bugs ... it still seems to be not solved.
You may want to confirm the bug on launchpad to increase the importance. You may want to check out this answer as well -> Num-Lock LED state does not correspond with internal state.

Community
  • 1
cl-netbox
  • 31,163
  • 7
  • 94
  • 131
  • It happens when starting to type too early after booting the computer. It also happens when opening an application with root privileges too early. If you wait about one or two minutes, it works flawlessly - not really. My computer always has a minute or two between I boot it up and log in. The problem also happens often while I am using the computer, long after I turn it on and even [some time] after I fix the glitch by pressing the NumLock button twice. Needless to say I don't run programs with root privileges every day as well. – Ivan Aug 16 '16 at 18:53
  • +1 Confirmed and subscribed and added a link from my answer here where I remembered mentioning this issue. Hopefully we can drive more traffic to the bug report and this will eventually be fixed. :-) – Elder Geek Apr 21 '17 at 21:20