Summary: | Case of autorepetition even with all keys physically up. | ||
---|---|---|---|
Product: | xorg | Reporter: | Octavio Alvarez <octalfdo> |
Component: | Input/Keyboard | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
URL: | http://web.archiveorange.com/archive/v/Ky751V5Yp70TRzlmvsit | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Octavio Alvarez
2010-05-30 22:52:40 UTC
Any news on this one? Octavio, how does the debug statements I got in this comment look like for you?: https://bugzilla.kernel.org/show_bug.cgi?id=9448#c42 Can we out of this conclude if it is a kernel bug or xorg bug? Or does this only happen when you actually turn off autorepeat when a key is pressed? Why would you want to do that? Well, no news. We found a way to work around the bug. > https://bugzilla.kernel.org/show_bug.cgi?id=9448#c42 Well, that doesn't seem to be a similar issue, but it does not seems to be the same one. I remember testing the console with "showkey" back then, and everything came out allright. > Can we out of this conclude if it is a kernel bug or xorg bug? No. > Or does this only happen when you actually turn off autorepeat > when a key is pressed? Why would you want to do that? Yes, because the program uses a "magic" key to enable itself and it must be held down for the program to work. Also, the program doesn't want logical presses and releases, only physical presses and releases. I would also like to link Daniel Stone's response on the mailing list to this bug report: http://www.mail-archive.com/xorg@lists.freedesktop.org/msg11460.html 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.