STEPS TO REPRODUCE 1. In the settings of the keyboard set "Numblock after Plasma restart" to "Leave unchanged" (I translated this from German to English. Don't know, if this 100% correct). Actually this was the default value. So I didn't have to set this. 2. Enable numblock 3. Restart your system OBSERVED RESULT Numblock is disabled EXPECTED RESULT Numblock should be enabled SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I think this is a 15 minutes bug
Are you using Wayland or X11? Depending on investigation, we may need to re-open Bug 368063.
I'm using X11
OK, seems like a slightly different issue. Is there any chance your machine's BIOS has a setting for the num lock behavior and it's currently set to automatically disable on boot? Can you check?
Quite the opposite: It is enabled. Had never this problem with Windows, Gnome or the old Ubuntu desktop Unity. Have this PC since 2017. If I enable numlock in KDE settings, then it works.
Created attachment 149383 [details] BIOS numlock settings
Ok, so your BIOS is trying to enable Num Lock on boot. Now, what happens in each of the following states: 1. System Settings is configured to enable Num Lock 2. System Settings is configured to disable Num Lock 3. System Settings is configured to leave Num Lock unchanged (I think we already know this one, right? It turns it on)
1. System Settings is configured to enable Num Lock --> Enabled 2. System Settings is configured to disable Num Lock --> Disabled 3. System Settings is configured to leave Num Lock unchanged --> Disabled, even if was manually enabled before shutdown.
Thanks for the info!