Created attachment 24915 [details] X server configuration file This bug was lately discussed in another bug report #8411, and Peter Hutterer asked to open a separate bug report. The original reporter didn't, so I'm doing the job. Conditions: Acer laptop with its own keyboard USB wireless keyboard Debian Sid amd64 kernel 2.6.29.1 kernel 2.6.28.9 Description: When the caps lock or the num-lock are pressed on the external keyboard, the relative LEDs don't turn on even if the state is properly changed. Switching to one of the consoles (ctrl+alt+F1) at least shows that num-lock behaves normally, but caps-lock still has the same problem. I can confirm both these points: 1 - "The CapsLock key behaves very strange. The LEDs are updated independently and correctly. However, when activating CapsLock on one (let's call it keyboard A), both keyboards actually produce capital letters, except for the first letter typed on keyboard B. That is, every time I typed something on keyboard A, the next letter typed on B will be lowercase. Keyboard A gives only uppercase." 2 - "When activating CapsLock on both keyboard (order does not matter), they both capitalize every first letter typed, the rest is lowercase. By every first letter, again I mean after typing on the other keyboard."
Created attachment 24916 [details] X server log
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/575.
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.