https://bugs.kde.org/show_bug.cgi?id=477374
Bug ID: 477374 Summary: Plasma on Wayland fails to recognize numlock status on startup Classification: Plasma Product: kwin Version: 5.27.8 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: guido-kdeb...@unknownsite.de Target Milestone: --- 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 -- You are receiving this mail because: You are watching all bug changes.