keyboard freezes when holding any key and pressing »CTRL«

Bug #397004 reported by piggy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I can reproduce this:
If i hold the LEFT-Cursor Key and press CTRL (LEFT+CTRL as in CTRL+c to copy) my Keyboard stops working. Mouse is still working.

[UPDATE];
Investigating a bit more systematic, I found out that this happens not only with LEFT+CTRL but with mostly __any__ key in Combination with +CTRL. (Even ENTER, Backsp, Tab, Esc, F1...F12 are affected)

The only exceptions are the following keys:
SHIFT
ALT
ALT_GR
CAPS_LOCK
NUM_LOCK
SCROLL_LOCK
BREAK
PRINT
META/Win-Key

Hope this helps!
[/UPDATE]

"Meta-keyboard-commands" outside of X (e.g. CTRL+ALT+BACKSP or CTRL+ALT+F1...) are still effective, therefore i can restart X and log in again. So i think, this is somehow related to X.

I haven't found anything interesting in .xsession-errors or /var/log/Xorg.0.log but i have attached them. I logged the output of xev while provocing the freeze:

<code>KeyPress event, serial 31, synthetic NO, window 0x3c00002,
    root 0x5b, subw 0x0, time 30918556, (71,-8), root:(149,88),
    state 0x2010, keycode 100 (keysym 0xff51, Left), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

FocusOut event, serial 31, synthetic NO, window 0x3c00002,
    mode NotifyGrab, detail NotifyAncestor
</code>

I have tested several keyboards (HP SDL4000 PS2; Cherry RS 6000 USB) and the problem ist reproducable with all of them, so this is not related to a special keyboard- or connection-type.

Further Information:
$ lsb_release -rd
Description: Ubuntu 8.04.3 LTS
Release: 8.04
$ uname -r
2.6.24-24-generic

I've attached:
* .xsession-errors
* var/log/Xorg.0.log
* etc/X11/xorg.conf
* deadkeyboard.txt (the full trace of xev)

Revision history for this message
piggy (konradbox) wrote :
piggy (konradbox)
description: updated
tags: added: freeze keyboard x11
Revision history for this message
Sergio Barjola (sbarjola) wrote :

Thank you for taking the time to report this bug. Can you add the output of "dmesg > dmesg.log" after reproducing the issue.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
piggy (konradbox) wrote :

Good to see, there's someone around ;-)

Attached is dmesg output after reproducing the error.

Revision history for this message
Sergio Barjola (sbarjola) wrote :

Can you get the /var/log/Xorg.0.log and dmesg output while the keyboard is freeze, switching to a Virtual Terminal ?
Thanks in advance.

affects: ubuntu → xserver-xorg-input-keyboard (Ubuntu)
Revision history for this message
piggy (konradbox) wrote :

I am not sure what exactly you are after:

* the output resulting from the keyboard-freeze? OR
* the output produced by switching to a VT?

So i did 2 log-sessions.

The first "viassh" from a remote machine, recording 3 states:
(contained in the *.viassh.zip)
"before" - before the freeze,
"after" - after the freeze, and
"vt" - after switching to a VT on the affected machine.

Here is what diff gave me:

$ diff xorg.viassh.before.txt xorg.viassh.after.txt
$ diff xorg.viassh.before.txt xorg.viassh.vt.txt
1013a1014,1015
> (II) Screen 0 shares mem & io resources
> (II) Screen 1 shares mem & io resources
$ diff dmesg.viassh.before.txt dmesg.viassh.after.txt
$ diff dmesg.viassh.before.txt dmesg.viassh.vt.txt
$

So - as far as I can see - the only thing that makes a difference ist switching to a VT.

The second log session was made exclusively on the affected machine recording only two states:
(contained in the *.vt.zip)
"before" - before the freeze and
"vt" - after the freeze, switching to a VT.

In short: there was no difference to the former.

$ diff xorg.before.txt xorg.vt.txt
1013a1014,1015
> (II) Screen 0 shares mem & io resources
> (II) Screen 1 shares mem & io resources
$ diff dmesg.before.txt dmesg.vt.txt
$

I'm afraid this does not bring any further insight?

So let me know, what else can I provide you with!
Thanks, Konrad

Revision history for this message
piggy (konradbox) wrote :

Updated title & description, because I found out there are much more possible key combinations.

description: updated
summary: - keyboard freezes when pressing »LEFT«+»CTRL«
+ keyboard freezes when holding any key and pressing »CTRL«
Changed in xserver-xorg-input-keyboard (Ubuntu):
status: Incomplete → New
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Please try the same with a ubuntu 9.10 or lucid alpha1 livecd.

Changed in xserver-xorg-input-keyboard (Ubuntu):
status: New → Incomplete
Timo Aaltonen (tjaalton)
affects: xserver-xorg-input-keyboard (Ubuntu) → xorg-server (Ubuntu)
Revision history for this message
piggy (konradbox) wrote :

Hi!
Tried with 9.10 i386 livecd and could not reproduce the error.
So what are the next steps?

Revision history for this message
piggy (konradbox) wrote :

Sorry for just bumping this issue, but as 8.04.3 is _LTS_ I would really appreciate further assistance with fixing this bug.
Thanks in advance!

Revision history for this message
Bryce Harrington (bryce) wrote :

Assuming fixed in development version since could not reproduce there.

Feel free to nominate this bug for Hardy if you'd like the issue considered for the LTS, but be aware that by now generally only security issues are being considered for hardy. If someone can propose a patch it might stand a higher chance.

Changed in xorg-server (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
piggy (konradbox) wrote :

What exactly do you mean by "development version"? A more proceeded 8.04 branch or just the current/next release (9.10/10.04)?

Since I have no clue where this originates from, it is hard for me to fix my long term intended production machine. I understand, this bug won't be examined by Ubuntu developers, for it is not security related. However, if anyone who had a look into my logfiles could just point me to a direction what possibly goes wrong on my installation, I'd be really happy to work out a solution myself.

Thanks for your commitment!

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.