Xorg not responding to input using forwarded X window

[John Johansen]

Binary package hint: xorg

Xorg stopped responding to input from the keyboard and mouse. The
mouse cursor still moves, notifications are still being displayed,
but input from mouse and keyboard have no effect.

The vt can be switch to and is working, switching back and forth has
no effect.

ProblemType: Bug
Architecture: i386
Date: Wed Aug 12 23:09:28 2009
DistroRelease: Ubuntu 9.10
MachineType: LENOVO 7762WGS
Package: xorg 1:7.4+3ubuntu5
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-5-generic root=UUID=11f5ccce-0c65-4480-8e69-8b77cae05c1a ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.5-1ubuntu1
 libdrm2 2.4.12-1ubuntu1
 xserver-xorg-video-intel 2:2.8.0-0ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu5
SourcePackage: xorg
Uname: Linux 2.6.31-5-generic i686
Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Can't open display
dmi.bios.date: 03/12/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7SET37WW (1.23 )
dmi.board.name: 7762WGS
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7SET37WW(1.23):bd03/12/2009:svnLENOVO:pn7762WGS:pvrThinkPadX61Tablet:rvnLENOVO:rn7762WGS:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7762WGS
dmi.product.version: ThinkPad X61 Tablet
dmi.sys.vendor: LENOVO
fglrx: Not loaded
glxinfo: Error: command ['glxinfo'] failed with exit code 255: Error: unable to open display
setxkbmap: Error: command ['setxkbmap', '-print'] failed with exit code 255: Cannot open display "default display"
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-5-generic
xdpyinfo: Error: command ['xdpyinfo'] failed with exit code 1: xdpyinfo: unable to open display "".

[Diggory (diggory-hardy)]

I've possibly been hit by the same bug... not been able to track it down much yet. It may be different because the symtoms are different:
Everything starts fine, then inactive applications stop responding to mouse clicks. Active applications vary, sometimes fine, sometimes they don't work either, at least twice the only thing that worked was scrolling down with the mouse wheel (couldn't click or scroll back up).
Keyboard input has always been fine.

I noticed the OP has a thinkpad X61; my machine is a T61 so may well have similar hardware. I'm running jaunty with latest updates; nvidia binary driver.

Still got to work out what's actually causing this; did think it was kde 4.2, but xfce had the same problem.

[John Johansen (jjohansen)]

Now that you mention it, I did have weird application input errors very similar to what you describe a few hours before this complete lock up. At the time I attributed it to the network as I doing a git clone and several of the apps were X forwarded from another machine.

Also I was working in a forwarded X window when the input freeze happened.

[Bryce Harrington (bryce)]

Hi John,

Are you able to reproduce this bug? If so, can you give the steps necessary for reproducing it?

Fwiw, often in the past when I've seen bugs with this specific set of symptoms, it's been because the hal process had died for some reason. X depends on hal for input, so if it goes away, so goes input. So this is something you might check for; if this is the case, then this would actually be a hal bug.

[John Johansen (jjohansen)]

Bryce,

I haven't been able to reproduce since Friday when X completely locked up on me and would kill all input once it started. This was consistent behavior and would happen every time I started X, either through gdm at startup or using startx. This is when I finally did a complete reinstall. Friday's behavior was exceptional, as this began occurring after a failed update.

However I haven't been doing any X forwarding this week so I haven't been able to test that portion of the bug. I will see if I can reproduce with X forwarding over the next few days.

[John Johansen (jjohansen)]

well I have not been able to reproduce. I have been using X forwarding extensively for the last few days, and no problems with input.

[Bryce Harrington (bryce)]

Hmm, okay well guess we can chalk it up to weirdness caused by the failed update; it's certainly not unusual to see bad behavior when the system is in an inconsistent state. We'll consider it fixed for now, but reopen the bug (or file a new one with ubuntu-bug xorg) if you find a way to reproduce it.