https://bugs.kde.org/show_bug.cgi?id=505550
Bug ID: 505550
Summary: NumLock startup setting ignored when BIOS NumLock is
enabled
Classification: Plasma
Product: plasma-login
Version First unspecified
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: kde-...@ferenz.org
CC: k...@davidedmundson.co.uk, olib...@outlook.com
Target Milestone: ---
SUMMARY
When NumLock is enabled in the BIOS/UEFI firmware, Plasma ignores the user
setting "Turn on NumLock at startup" (from the Keyboard Hardware settings).
Even with autologin enabled, this setting is expected to override the firmware
state, but it does not.
If NumLock is disabled in BIOS, Plasma correctly applies its own setting —
NumLock is enabled at session start, as expected.
This leads to confusion, especially because:
- There is no warning or indication in the GUI
- The setting is available in KDE System Settings, but simply ignored
Steps to reproduce:
1. Enable NumLock in BIOS
2. Enable "Turn on NumLock at startup" in Plasma's Keyboard settings
3. Enable autologin (optional)
4. Reboot the system
Expected:
Plasma activates NumLock regardless of BIOS state
Actual:
NumLock remains in BIOS-defined state; Plasma setting is ignored
Workaround:
Disable NumLock in BIOS – Plasma setting then works as expected.
Tested on:
- Fedora 42
- KDE Plasma 6.3.5
- Wayland session
May be related to bug 454478, but this was tested on Plasma 6.3.5 and Wayland
with autologin enabled.
--
You are receiving this mail because:
You are watching all bug changes.
