1. Start the first X server: startx 2. Hit the NumLock to let the NumLock LED on (my default state of NumLock is off) 3. Switch to another console and start second X server: Ctrl+Alt+F1, startx -- :1, the NumLock is off, so is NumLock LED 4. Switch to the first Xserver, the number keyboard is working though NumLock LED is off; it needs to be hit twice to correct the state.
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
The same problem has been reported by Kurt Roeckx in the Debian BTS (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418298), and I can reproduce here with the latest release. You don't even need to start a second X server to reproduce. Just switch to a virtual text console and then back to X. The numlock LED will be off while numlock seems to be enabled.
Problem still exists, with: kernel 2.6.35 xorg-server:1.8.1.902 evdev input driver either Nvidia or nouveau driver without: xorg-input-kbd
This is a mass change of bugs. Bugs assigned to me that haven't been updated in the last 3 years are closed as WONTFIX, because, well, let's at least be honest about it. Please do not re-open unless you have a really good reason to do so (e.g. you're fixing it yourself). If it hasn't been fixed in the last 3 years, it probably won't be fixed anytime soon either. Sorry.
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.