Bug 454478 - "Leave unchanged" num lock setting disables num lock on boot when it was previously enabled and the relevant BIOS setting enables it too
Summary: "Leave unchanged" num lock setting disables num lock on boot when it was prev...
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keyboard (other bugs)
Version First Reported In: 5.24.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: stefano.d
URL:
Keywords:
: 432107 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-05-27 10:37 UTC by stefano.d
Modified: 2025-01-14 17:54 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
BIOS numlock settings (634.85 KB, image/jpeg)
2022-06-01 17:10 UTC, stefano.d 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description stefano.d 2022-05-27 10:37:52 UTC 
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
Comment 1 Nate Graham 2022-05-27 14:22:36 UTC 
Are you using Wayland or X11?

Depending on investigation, we may need to re-open Bug 368063.
Comment 2 stefano.d 2022-05-27 15:46:10 UTC 
I'm using X11
Comment 3 Nate Graham 2022-06-01 16:00:48 UTC 
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?
Comment 4 stefano.d 2022-06-01 17:10:41 UTC 
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.
Comment 5 stefano.d 2022-06-01 17:10:59 UTC 
Created attachment 149383 [details]
BIOS numlock settings
Comment 6 Nate Graham 2022-06-02 14:57:16 UTC 
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)
Comment 7 stefano.d 2022-06-03 20:41:32 UTC 
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.
Comment 8 Nate Graham 2022-06-06 17:43:59 UTC 
Thanks for the info!
Comment 9 TraceyC 2025-01-14 17:53:40 UTC 
Tested with a laptop that does not have a numlock setting in BIOS and an external keyboard with a numlock key
Can reproduce on git-master with both X11 and Wayland

1. Numlock on startup setting: Leave unchanged
2. On the keyboard, set numlock on 
3. Rebooted

Observed: Numlock was off
Expected: Numlock is on

This complaint goes back to 5.20.90 and January 2021. See bug 432107
From that report, the behavior *might* be intentional, but clearly it's not what users expect
From the user's POV, that setting means "KDE will set numlock to whatever it was when I logged out"
Comment 10 TraceyC 2025-01-14 17:54:51 UTC 
*** Bug 432107 has been marked as a duplicate of this bug. ***