-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2016-04-07 at 08:17 +0200, Per Jessen wrote:
Carlos E. R. wrote:
Any chance it might be a hardware issue? It really sounds weird for the NumLock LED to be lit without the numerical keypad being active.
Not at all. You can toggle the LED alone by software. I played with that on another life.
Probably, but it still sounds weird that it should happen.
Of course. But the thing is, the LED in the keyboard is set from the computer, and independently, somewhere else in software there is a status kept for upper/lower case. And in Linux, one for graphics, another for text, and maybe one per seat login. To complicate things, I don't think the LED status can be read. That explains why the "real" status and what the LED says can be different. If I remember correctly, the keyboard sends the same key codes regardless of the LED or keyboard flag status. Ie, it is the software which reads 'a' then thinks "no, it is 'A'". But this I'm not sure at the moment, it has been more than a decade since I played with these low level things. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlcGULwACgkQtTMYHG2NR9V+rQCePz35aLVCiTtq9lg2ixCo1jMJ vBIAniKenlQ+50LcPT+zIQ/MHNHbfgBA =jwrm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org