dual head X crashes when generating keyboard event on the external display

[washeck]

Binary package hint: xorg

I upgraded my Toshiba Tecra M9 laptop from Xubuntu 8.10 to Xubuntu Jaunty alpha from today. I use nvidia driver 180 and have an external display connected to the laptop configured as a separate X screen with Xinerama. I also ran "dontzap -e" command after the upgrade.

The crash is 100% reproducible.

Steps to reproduce:
1) Boot the laptop with external display connected
2) Login to xfce
3) Move mouse cursor to the external screen
4) Generate a few keyboard events (2-3 keyboard presses are enough) - e.g. push down arror or 'z' a couple of times
5) X crashes and restarts to login screen

If I generate mouse clicks on the extarnal screen, no crash happens. Also using the laptop screen with no activity on the external screen is OK.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: xorg 1:7.4~5ubuntu12
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-6-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-3ubuntu1) ) #17-Ubuntu SMP Fri Jan 30 15:34:36 UTC 2009

SourcePackage: xorg
Uname: Linux 2.6.28-6-generic i686
Xrandr:

[washeck (vrehak)]

Is there anything I can do to help triaging this bug? It seems to me like a serious problem (dual-head setup is unusable on my laptop). I'm not reporting it upstream as I don't know if the problem is Ubuntu specific, Xorg bug or NVidia bug.

[Bryce Harrington (bryce)]

Hi vrehak,

Could you please collect a full backtrace from when this crash occurs? Directions on collecting full backtraces are at https://wiki.ubuntu.com/X/Backtracing

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[washeck (vrehak)]

Bryce, I was not able to gather a better backtrace (partially due another bug in nvidia drivers that prevents me from switching to console if X is running) but anyway the problem seems to be gone. I guess it was fixed by update to nvidia-glx-180 to 180.44-0ubuntu1 or one of the earlier updates to nvidia driver. You can close this bug report.

[Bryce Harrington (bryce)]

Thanks for letting us know the issue is resolved.