This feature is temporarily broken. My preferred workaround uses xdotool (great for desktop automation), install if not already present. Place the following line in a startup script, or can be added to ~/.bashrc if terminal opens on startup:
xdotool key Num_Lock
To make persistent across suspends/hibernates, create (as root) /etc/pm/sleep.d/90_numlock-temp-fix with the following contents:
#!/bin/bash
case "$1" in
resume|thaw)
xdotool key Num_Lock
;;
esac
Backstory: The following two keys should work to both set numlock on and make that the default bootup state.
Unused keys are typically a tipoff that the object controls are in a state of flux. There are several dealing with numlock so expect this to be fixed, hopefully in the next minor release (which should be out any time now?).
If these two keys are already set, watch for the bootup numlock state to return to 'off', which means the bug is fixed and this workaround can be removed. (Numlock will then boot 'on'.)
Thanks to this video,
I installed numlockx
then setup a startrup application with "numlockx on" as the command.
You can just set gnome to remember the Num Lock state between boots:
On Ubuntu 20.04.1
Source French: https://doc.ubuntu-fr.org/numlockx
Add this line after install numlockx:
greeter-setup-script=/usr/bin/numlockx
on file "50-slick-greeter.conf"
Path to diretory:
No additional package needed, just follow this pathway:
This feature is temporarily broken. My preferred workaround uses xdotool (great for desktop automation), install if not already present. Place the following line in a startup script, or can be added to ~/.bashrc if terminal opens on startup:
To make persistent across suspends/hibernates, create (as root) /etc/pm/sleep.d/90_numlock-temp-fix with the following contents:
Backstory: The following two keys should work to both set numlock on and make that the default bootup state.
In 20.04.1, at least so far, they are ignored.
Unused keys are typically a tipoff that the object controls are in a state of flux. There are several dealing with numlock so expect this to be fixed, hopefully in the next minor release (which should be out any time now?).
If these two keys are already set, watch for the bootup numlock state to return to 'off', which means the bug is fixed and this workaround can be removed. (Numlock will then boot 'on'.)
Num-Lock can be set on the Input devices page in settings. BUT some computers set this in Bios. Boot to the Bios and look for it there as well.
From the K-Menu > Settings > System Settings > Input Devices (under Hardware) > Keyboard
The first option is "NumLock on Plasma Startup" just turn it on.
Addition answer @Daniel Pablo Sheng: In Xubuntu 20.04 for me work this:
reboot
The "NumLock on Plasma Startup"-Option in Kubuntu 20.04 doesn't work.
Just installing numlockx from repository does the job.