[gutsy] [regression] xorg crashes with segfault after having used displayconfig-gtk to set up a second display (new "intel" driver)

[Vincenzo Ciancia]

Binary package hint: xorg

I have used displayconfig-gtk with a second display attached to my laptop. I have an intel video card recognized by lspci as

00:02.0 0300: 8086:27a2 (rev 03)
00:02.1 0380: 8086:27a6 (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)

Gutsy setup has chosen for me the new "intel" driver which achieves higher resolutions than before. After the setup using displayconfig, the X server crashes with segmentation fault (signal 11), with or without second monitor attached. Previous configuration found in /etc/X11/xorg.conf.1 works perfectly.

Going to attach the X server log, the new (broken) and old (working) configuration files.

[Vincenzo Ciancia (vincenzo-ml)]

I confirm that this is not happening with the "i810" driver. In that case, the configuration file does not make xorg crash, even though second display settings are completely ignored.

[Tormod Volden (tormodvolden)]

Thanks for your bug report. Can you please install a debug build of the intel driver, or the xserver-xorg-video-intel-dbg package if it exists? It might help to get more info from the backtrace in the log.

[Tormod Volden (tormodvolden)]

I reported a similar issue in https://bugs.freedesktop.org/show_bug.cgi?id=12295, but for an ATI card. A complete backtrace might tell if it is the same issue.

[Tormod Volden (tormodvolden)]

I think you can get a debug package here: http://people.ubuntu.com/~ubuntu-archive/ddebs/pool/main/x/xserver-xorg-video-intel/

[LarsIvarIgesund (larsivar)]

I get a crash at X startup after trying to set up dual screens via KDE system settings, having the intel X3100 chipset.

Attaching the created xorg.conf and Xorg.0.log which has the backtrace at the bottom.

[LarsIvarIgesund (larsivar)]

The promised Xorg.0.log with the backtrace ...

[Tormod Volden (tormodvolden)]

You should probably try using xrandr to setup dual-head, instead of displayconfig-gtk, see http://www.intellinuxgraphics.org/dualhead.html

LarsIvarIgesund, you have the same backtrace as Vincenzo. You didn't install the debug package either?

[Vincenzo Ciancia (vincenzo-ml)]

I am slightly busy at the moment but I promise I will make the backtrace ASAP, however, is there an option to debuild to build a debug package so that I can build the most recent version? Thank you.

[Tormod Volden (tormodvolden)]

Yes, you can set
 export DEB_BUILD_OPTIONS="debug noopt nostrip"
before you run debuild.

[Vincenzo Ciancia (vincenzo-ml)]

I compiled the intel video driver using options that you suggested but the backtrace remains the same, I attach it for reference.

[Tormod Volden (tormodvolden)]

Thanks. I guess the stack is corrupted and breaks the stacktrace. To verify the debug build, run "file /usr/lib/xorg/modules/drivers/intel_drv.so" and it should say "not stripped".

[Vincenzo Ciancia (vincenzo-ml)]

Ok, I can confirm that I I produced the backtrace using a debug build of the driver.

[Thom Pischke (thom-pischke)]

Also having this issue with the Dell Inspiron 1420n after upgrading to gutsy. Removed the i810 driver and installed the 'intel' driver. Most stuff works nicely, but 3D was actually faster with the 'vesa' driver in xorg.conf, and sadly, the dual monitor configuration UI (my main motivation for upgrading) just crashes and trashes my xorg.conf, forcing a restore from backup. A bit disappointing, since I bought this laptop with linux compatibility as the primary motivation.

I'm not too worried, as I know the intel driver and xrandr, etc are all still under heavy development, but wanted to add my experiences to the issues. Me too!

[Tormod Volden (tormodvolden)]

displayconfig-gtk sets up xorg.conf to use Xinerama (and "zaphod" mode). The new intel and ati drivers don't support Xinerama any longer, and xrandr must be used, like described in that Intel howto linked above. Therefore displayconfig-gtk must be fixed. OTOH, the X server should not crash because of this configuration, but just ignore it and give a warning message, in the ideal case.

[unggnu (unggnu)]

This is fixed in latest displayconfig-gtk afaik.

[Bryce Harrington (bryce)]

ungnu, thanks. Marking as fixed.