https://bugs.kde.org/show_bug.cgi?id=432107
--- Comment #7 from Claudius Ellsel <claudius.ell...@live.de> --- (In reply to Wolfgang Bauer from comment #5) > (In reply to Claudius Ellsel from comment #0) > > Also, Ideally that would already work at either Kernel > > or SDDM level, not sure what causes the problems there. > In that case, it should be reported to the kernel or SDDM though. > > At least SDDM does have a setting for this: > Numlock= > Change numlock state when sddm-greeter starts. Valid values > are on, off > or none. If property is set to none, numlock won't be > changed. Default > value is "none". Yup, just wanted to make sure first that I get the scope of the problem correctly. As I wrote before, NumLock is already off for SDDM. Does the `none` value there also means that it is supposed to read the BIOS value or just that it doesn't touch NumLock at all meaning when the Kernel has turned it off it will just stay at that? -- You are receiving this mail because: You are watching all bug changes.
