SUMMARY *** Num lock is turned on, but it has to be turned off, then turned on again to be able to press any numbers from the keypad when typing passwords for the lock screen or KDE Wallet. This issue did not exist when I was using Kubuntu 22.10, but it noticed it after updating to Kubuntu 23.04. *** STEPS TO REPRODUCE 1. Go to lock screen. 2. Try to press any number from key pad. OBSERVED RESULT Numbers can only be pressed after turning numlock off, then turning it on again, despite being turned on during startup from keyboard settings. EXPECTED RESULT Numlock to be turned on during startup. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.04 KDE Plasma Version: KDE Plasma 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION The issue happens everytime the screen is locked then unlocked, or when typing password for KDE Wallet.
When using Wayland instead of X11, I can use the keypad when typing the password to KDE Wallet without having to turn numlock off and on again, but the issue still exists with lock screen.
To be clear, the issue with lock screen happens does not happen after logging in under Wayland. This confirms that this issue is related to X11, and not Wayland.
I am sorry, there is a typo in my previous comment. The correction: "To be clear, the issue with lock screen does not happen after logging in under Wayland."
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with either Plasma 5.27.11 (the current LTS version) or Plasma 6.2.5 (the latest released version)? If you can still reproduce the bug, please change the Status to "CONFIRMED". Thanks.
The last time I used KDE Plasma (6.2.3), I was able to turn Num Lock automatically by using a workaround, but I encountered a fatal bug with KDE Plasma that I couldn't fix, and I decided to use Cinnamon DE and Debian Stable for the maximum stability, so I can't confirm if this issue is fixed or not.
Thanks for the update. I'm sorry to hear you had a bug you couldn't work around. Best of luck with your current setup :)