[Bug 483232] autorepeating or dead keyboard
http://bugzilla.novell.com/show_bug.cgi?id=483232
User jkosina@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=483232#c16
--- Comment #16 from Jiri Kosina
It is internal laptop keyboard.
So probably conntected through PS/2, right? (you can find out from dmesg or hwinfo --keyboard, for example).
- capture both evtest and xev output on the keyboard device from the situation when the key is stuck, to see if it is X or kernel who loses the release event
I don't think we understand each other. First of all what does "when" means here?
Second -- by "stuck" I guess you mean autorepeating case. Such case looks like this, I press a, b, c keys. I get
abbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbc
And for next several hours everything can be fine. So in practice I can do only tests _after_ autorepeating occurs. And after additional keys pressed -- because I cannot predict when it happens, and since I am fast typist I type faster than I track the output.
Would id be possible to keep capturing evtest traffic all the time, and when you experience this loss of release event (i.e. wrong autorepeat of the key), extract the relevant part from the saved evtest output and attach it to this bug? Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com