Summary: | "Leave unchanged" num lock setting disables num lock on boot when it was previously enabled and the relevant BIOS setting enables it too | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | stefano.d |
Component: | kcm_keyboard | Assignee: | stefano.d |
Status: | REPORTED --- | ||
Severity: | normal | CC: | butirsky, nate |
Priority: | NOR | ||
Version: | 5.24.5 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=368063 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | BIOS numlock settings |
Description
stefano.d
2022-05-27 10:37:52 UTC
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! |