Ever since upgrading from FC1 to FC2 (the 1st xorg) then FC3, I've been plagued by weird keyboard repeat rate behaviour. The core problem is that the repeat rate I set in the GNOME keyboard preferences GUI is not usually honoured. I use a very fast repeat rate of around 50-60cps (guessing) since RH(9?) allowed >30. I also have a very short delay (probably 50ms?). What will happen is I will start X (via startx) and the repeat rate will work fine (usually) for a while. Then for no reason it will start acting weird. I will see one of: 1. repeat rate slows down to a constant 30(ish) cps 2. repeat rate will be as fast as I desire for about .5 second then drop to 30 3. repeat rate will be as fast as I desire for about .5 second then drop to agonizing speeds, like 5 cps 4. once it starts going wonky, the GNOME preferences setting will have no effect on the rate Occasionally the rate will change during my session (which is usually weeks) between these options! For no apparent reason! I even *think* I've seen the numlock light go off at points for no reason whatsoever, but I can't be positive on this one. I've tried driver "kbd" and "keyboard" in the conf file. Both behave slightly differently but the symptoms always follow the above 3 at some point. 2 other people have reported the same problem. There is a redhat bugzilla bug open on this: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134110 I use a KVM with an old "clicky" expensive IBM PS2 keyboard and a new-ish PS2 mouse. One other reporter says he doesn't use a KVM. This exact same gear has worked perfectly for me with never a repeat rate problem since RH6.1! It was just when I put in FC2 with x.org that it all went wonky.
The bug just hit me again and I was able to note the precise effects in much more detail this time as it was really strange. After using X for roughly 5 hours all of a sudden, while I was typing but taking a quick break to think, the system acted like I was holding down the spacebar and put about 30 spaces into my window at high speed. I must have freaked and hit a key and it stopped it. I definitely had not typed a space within a few seconds of that happening. AND I noticed for sure this time that right as this happened the num lock key LED turned off! And even though the numlock light is off, the system still thinks numlock is on (the keys still produce numbers)!! Now I just tapped num lock and the light stayed off (ie: no toggle). I tapped it again and it went on. And now my keyboard repeat rate is down to the stock 30cps (it feels like). I'm using driver "kbd" this time. I will be testing the FC3 rawhide pre-6.8.2 packages shortly to see if they fix anything.
*** This bug has been marked as a duplicate of 1651 ***
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.