"Key stuck" after switching workspace in Gnome with Keyboard shortcut

Bug #376485 reported by Rolf Leggewie
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-input-keyboard (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I run an up-to-date Jaunty system. I've experienced this problem since about February when I moved from hardy to jaunty.

Not sure where this bug is hiding. I'm using Gnome, but I have quite a bit of trouble with keyboard entry where I suspect scim is the culprit. Help in pinpointing the issue greatly appreciated.

I have four workspaces. It happens at times (not always, but frequently enough to be annoying, about 25% of the time, I'd say) that when I use Ctrl+1 to switch to the first workspace for example, that a string of "11111111111111" is continually input into any text field in the active window on that workspace. It's almost as if the 1 key was stuck (which is not the case). When I go to Ctrl+2, it will be "2222222222". Hitting Esc will usually end any further input. But almost any key I hit (such as backspace for deletion) will output another "1" or "2" character. The character is always the same as the workspace number that I just switched to.

If I was using VoIP at the time this happened, the partner on the other end of the line and me will hear a regularly recurring beep sound. I'd say the frequency is either once or twice per second.

"dmesg|grep kbd" right after this happened will get me "[194092.286510] atkbd.c: Spurious NAK on isa0060/serio0. Some program might be trying access hardware directly."

Although similar, I don't think I am seeing bug 124406 for the reasons I have given there.

Rolf Leggewie (r0lf)
description: updated
description: updated
Rolf Leggewie (r0lf)
description: updated
Revision history for this message
Rolf Leggewie (r0lf) wrote :

I recompiled kernel git HEAD the other day and the problem is present there, too. If this is a kernel bug, it is not specific to Ubuntu patches and still unresolved upstream.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

My feeling is that this is a problem in Jaunty and Karmic Xorg.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid or Maverick packages ?
Tanks in advance.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Fabio, your second comment is useless. Please stop doing that kind of "triage". Can you imagine that it's not clear what package a bug is in? If you know what the correct package is, refrain from this useless, lecturing type of comment and just assign the bug to that package.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

this is a hardware specific issue. I only experienced this on my Thinkpad under high load (and I believe only with a particular version of X). I haven't used the Thinkpad for quite a while and will need to retest.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Let me understand, you have open gedit on workspace 1 and hit ctrl+2 to go to workspace2 and in gedit appear 22222222222 ?
Ok ?

Revision history for this message
Rolf Leggewie (r0lf) wrote :

yes, that would be one example.

Please don't assign this bug to gedit now ;-)

affects: ubuntu → xserver-xorg-input-keyboard (Ubuntu)
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello Rolf.
I cannot reproduce this issue, but i think that is probably reconducible to xserver-xorg-input-kbd, that sometimes seems to miss full control of the inputs when an application with cursor is focused.
Then, please run in a terminal:
apport collect -p xserver-xorg-input-kbd 376485
Thanks
:)Fabio

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in xserver-xorg-input-keyboard (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.