This has happened twice so far (in about a day of working with xorg 1.6.99.901), both times on the same machine (while 2 other machines running the same software are ok), and both times under fairly heavy load (compiling stuff and playing a video at the same time): While typing, a key appears to get stuck, just repeating the character over and over, even long after the key has been released; at the same time, new key presses (such as Ctrl+Alt+Backspace) are ignored. ssh-ing in and restarting the X server fixes it; I doubt it's a hardware problem because this never happens while in text mode. Xorg-server 1.6.99.901 libXi 1.2.99.4 xf86-input-keyboard 1.3.99.1 linux 2.6.31 The keyboard is a USB Logitech Classic New Touch Keyboard (46d:c315).
Pressing the same key that is stuck doesn't help?
No, any input from the keyboard (including the same key) is ignored at the point. The mouse keeps working. Neither Xorg.0.log nor dmesg show anything unusual.
The problem appears to be specific to the kbd driver -- I've switched the box showing the problem to the evdev driver this morning and at least so far it hasn't caused any problems. (My other machines that don't have the problem use the kbd driver as well, so it's probably not a general kbd bug)
(In reply to comment #3) > The problem appears to be specific to the kbd driver -- I've switched the box > showing the problem to the evdev driver this morning and at least so far it > hasn't caused any problems. have you seen the bug in the last 3 days?
No, it went away after I switched xorg.conf over to using evdev. I'll switch back to kbd now to see if it keeps happening there
I can sort-of reproduce the issue, the key (very occasionally only) gets stuck, but hitting the stuck key stops it again. I suspect this is a race in the xkb autorepeat code triggered only by the kbd driver. Either way, since it's not reproducible with evdev and it's hard enough to reproduce with kbd I'm punting it to 1.7.1 instead. This won't hold up the release.
From user report, it seems that this happens especially when the system is under load. (The permanent issue from comment 2 not the one from comment 6)
I think this is the same issue that has been lengthily discussed in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/124406. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/124406/comments/269 credibly suggested that http://ajaxxx.livejournal.com/62378.html may have some information as to the root cause of this issue. Please have a look.
Is this bug still relevant? Is there a way to reproduce it, or do yo know where the race is, so it can be more easily reproduced by introducing a stall?
*** Bug 25669 has been marked as a duplicate of this bug. ***
Not certain whether this is a problem with the X server, but I experience similar probbbbbbblems when the machine is under load. Thisssssssssssssssssssssssssssssssss reeeeeeeeeeeeeeeeeeeeeeeeeeeeeegularly happens with this Bluetooth Lenovo keyboard in HID mode. Noooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooot sure hoooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooow to diagnoseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee it , but yyyyou can see the effecccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccts of normal typppppppppppppppppppppppppppppppppppppppppppppppppping right above....
The fact that it's a BT keyboard makes me wonder if you're experiencing an issue at the BT layer rather than in X11 itself. Do you have issues if you use the tty directly as well, or is it restricted to X11?
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.