Bug 35005

Summary: NumLock state on two USB keyboard LED-s
Product: xorg Reporter: Peeter Vois <peeter>
Component: Input/KeyboardAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED INVALID QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: alain.anderlini, chealer, peeter
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Peeter Vois 2011-03-03 23:19:35 UTC 
When connecting two USB keyboards to the computer running Linux/xorg, then they both act as single keyboard, which is OK. Pressing keys on one or another keyboard will result exactly the same and both keyboards share the same NumLock state.

The issue: The NumLock LED does change the state only on the keyboard where the NumLock was pressed, but the NumLock state is assigned to all USB keyboards. (Keyboard LED-s are controlled by OS)

Fix proposals:
1) NumLock LED state message is sent to all keyboards when changed.
2) All keyboards have its own NumLock, CapsLock, e.t.c state independent from other keyboards.

Other observations:
1) M$ Windows 7 does send NumLock LED status to all attached USB keyboards.
2) Laptop keyboards have its own driver / hardware numlock handling and therefore these can have independent numlock state. Although on Linux, it can get confusive: I've seen state where USB keyboards NumLock LED has to be OFF for the numpad keys to be handled as numeric keys on laptop.
Comment 1 Adam Jackson 2018-06-12 19:07:46 UTC 
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.