SUMMARY When starting up KDE Plasma (kde-plasma/kwin-5.27.8-r3) when NumLock is already enabled, it will leave the NumLock indicator on the keyboard on, but treat keyboard input as if NumLock were off. If the NumLock button is pressed in this situation, the internal NumLock status will stay off and the keyboard's NumLock indicator will go dark. STEPS TO REPRODUCE 1. Start up SDDM 2. Make sure NumLock is enabled 3. Log in to a Plasma on Wayland session OBSERVED RESULT 1 - After startup, the keyboard LED indicates the wrong NumLock status. 2 - NumLock is effectively off after Plasma start in all cases I have seen. EXPECTED RESULT 1 - The status of the keyboard's NumLock LED should always correspond 1-1 to how the system will interpret input on the NumPad. 2 - If NumLock is enabled before Plasma starts up, it should still be enabled after startup unless intentionally disabled by the user. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux 6.1.62, Plasma 5.27.8 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION While I am reporting this for kwin version 5.27.8, I have seen this behavior in all versions of kwin on Wayland I have tried so far. I have not seen it in kwin on X. See also the corresponding bug report in the Gentoo bug tracker: https://bugs.gentoo.org/917749
I found this bug when I was researching why the Numlock state is "off" even though I have set Settings -> keyboard ->Hardware -> NumLock on Plasma Startup to "on" Plasma 6 with a Wayland session As a workaround, under Advanced, I enabled "Numeric keypad always enters digits (as in macOS) Operating System: Solus 4.5 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.8.10-291.current (64-bit) Graphics Platform: Wayland Processors: 16 × 11th Gen Intel® Core™ i7-11800H @ 2.30GHz Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: XPS 17 9710
Found an earlier bug for this, marking this one as duplicate. *** This bug has been marked as a duplicate of bug 368063 ***