Summary: | Wrong state of NumLock LED with 2 X servers started or state of NumLock LED is not preserved | ||
---|---|---|---|
Product: | xorg | Reporter: | Lukasz Wieczorek <lukaswu> |
Component: | Input/evdev | Assignee: | Peter Hutterer <peter.hutterer> |
Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | drdarkraven, lukaswu |
Version: | 7.5 (2009.10) | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Lukasz Wieczorek
2007-02-13 00:42:22 UTC
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.