FS#6876 - Keyboard keeps repeating chars

Attached to Project: Arch Linux
Opened by Georg Grabler (STiAT) - Wednesday, 11 April 2007, 06:29 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 16 May 2007, 18:42 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan de Groot (JGC)
Architecture i686
Severity Critical
Priority Normal
Reported Version 0.8 Voodoo
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hello,
Within an update yesterday, one of my PCs keeps repeating characters as if they were stuck, also described by another user in the following post:
http://bbs.archlinux.org/viewtopic.php?id=31785

This just occures on one out of 4 PCs, what might makes it hard to track.

There were quite a lot of packages updated, not just the kernel on this PC, so i'm not sure if it's kernel related or not (as the user describes he updated the kernel, i don't know if he didn't update other packages as well). If you need any additional information, jot down what you'd like to see and i'll provide them to you.

Critical, since it makes working on this machine impossible.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 16 May 2007, 18:42 GMT
Reason for closing:  Works for me
Additional comments about closing:  Can't reproduce it myself, original reporter says it's fixed. Guess it was a kernel issue in an older kernel.
Comment by Roman Kyrylych (Romashka) - Wednesday, 11 April 2007, 14:47 GMT
is this happening in both X and plain text console?
Comment by Pierre Schmitz (Pierre) - Wednesday, 11 April 2007, 20:20 GMT
I noticed the same problem on a quite old computer. It only appears within X and if I switch to vc (ctrl+F1) and back to X the problem is solved. It has to be a general problem with xorg beacause I noticed this a couple of month ago.
Comment by Jens Adam (byte) - Wednesday, 11 April 2007, 21:55 GMT
Got that too (in X) and the issue disappeared a few months ago. I remember something about "atkbd.c: Unknown key pressed" in dmesg. After that problem was gone I noticed the clock was going either too fast (per default) or too slow (depending on the kernel parameter I tested as workaround). Finally solved that problem with 'clocksource=pit' and that got also fixed by a recent kernel upgrade.
Comment by Georg Grabler (STiAT) - Friday, 27 April 2007, 11:58 GMT
I don't know what exactly i did (maybe another kenel upgrade), but it worked again some days later.

Loading...