X freezes when connecting external monitor

Bug #473952 reported by Dennis van Dok on 2009-11-04
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

When I connect an external monitor while being logged in, and subsequently trying to use it, either by pressing f7 or running xrandr or opening system -> preferences -> display, the displays freeze.

I can still remotely log in (via ssh) and look around; however, I could not kill the X server even with SIGKILL nor make a core dump.

I'm including the Xorg.0.log, which ends at the time of the freeze. Also included is a snippet of kern.log that may be relevant, and the output of lsof for the X process.

ProblemType: Bug
Architecture: amd64
Date: Wed Nov 4 10:20:54 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xorg
MachineType: Apple Inc. MacBook2,1
Package: xserver-xorg-core 2:1.6.4-2ubuntu4
ProcCmdLine: root=UUID=ecc72b10-8e9c-48fe-8528-00d1fc58ea7d ro quiet splash
ProcEnviron:
 LANG=nl_NL.UTF-8
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.15~git-0ubuntu0tormod~jaunty
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: xorg-server
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:2476): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2589): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2565): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:2564): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
 (Do:2586): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.
dmi.bios.date: 06/27/07
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB21.88Z.00A5.B07.0706270922
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F4208CAA
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F4208CAA
dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA:
dmi.product.name: MacBook2,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-14-generic

Dennis van Dok (dvandok-gmail) wrote :
Bryce Harrington (bryce) on 2009-11-04
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
FreeMinded (pascal-planetmages) wrote :

I can confirm this problem on a Lenovo ThinkPad X60 with Intel graphics. If external monitor is connected at startup it is possible to use it, but only if monitors are mirrored (to lower laptop sceen resolution) or the Laptop screen is turned off. Trying to activate both monitors at their respective resolution crashes the screens.

Dennis van Dok (dvandok-gmail) wrote :

Actually I'm able to use both screens in dual-head mode, but only if I connect the screen before booting, or if I log off then on again after connecting the screen (as this restarts the X server).

dvdmeer (dennis-dvdmeer) wrote :

Same problem here. When using xrandr (in this case via my application python-randr) after I have logged in: boom, screen is not usable anymore.. restarting the X (ctrl-alt-backspace) and everything works fine.

Changed in xserver-xorg-video-intel (Ubuntu):
importance: Undecided → Medium
Dimitrios Symeonidis (azimout) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #466539, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

Dimitrios Symeonidis (azimout) wrote :

Actually, it's a duplicate of #419328

To post a comment you must log in.