There is no problem in other OS. Default expected behavior for standart PC – is that you:
- Set up NumLock initial status in the bios
- It remains same in bootloader
- It remains same at login screen
- It remains same in desktop session, until you intentionally change it.
So here seems to be a problem, in some "malicious" code, that forcefully disables it, during boot. Question is: What exactly disables it? What binary? Or what source file? Can I remove it, at least locally, on my machine, in order to stop Ubuntu from changing NumLock state at boot?
Or maybe that's a tweak, like Troubleshooting features
> [V] Force disable num lock at boot
, that was occasionally enabled by default?
I've concluded some searches, what I've found is that:
- Official information is outdated. There is no such menu in Ubuntu Settings as per 18.04 LTS.
- A couple of threads, here and there, are also not answering where does the illness seats.
- Installing and using
numlockx
is a stub. Why do we need disable (initially enabled) NumLock, and then use additional software to re-enable it? Such an advice really sounds like somthing "conceptually wrong".
Can you help to find out, where is the disease source, and how to fight it?
Best Answer
For Ubuntu Gnome 18.04+
When you are at the login screen the user ID active is
gdm
(Gnome Desktop Manager). To change that profile login with your own user ID and use:For a plethora of even more options:
For Ubuntu Unity 16.04+
Install the the program
numlockx
:Next step is to get it running during login screen:
At bottom of file add:
Save file and login again.
Catchall when everything fails
Install
numlockx
as show above. ThenAt bottom of file add:
Save file and reboot.