displayconfig-gtk crashes on Test

[Justin Dugger]

Binary package hint: displayconfig-gtk

displayconfig-gtk crashes when I enable the second monitor and click "Test".
Steps to reproduce
1. Select Screen 2
2. Change from Disabled to Secondary Screen, Mirror default screen.
3. Click Test, a short graphical glitch occurs, which is understandable, and then displayconfig unexpectedly exits. Running from the command line outputs the following:
jldugger@jldugger-laptop:~$ gksudo displayconfig-gtk
on_button_test_config_clicked()
Got pid 14342
(0, 0)
displayconfig-gtk: Fatal IO error 104 (Connection reset by peer) on X server :9.0.
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS

This is the laptop on which I'm testing this. https://wiki.ubuntu.com/LaptopTestingTeam/ToshibaTecraM7

Let me know if there's a way to get more information needed to debug this.

[Justin Dugger (jldugger)]

I don't think this is a duplicate of 135387. My chipset is nvidia (Quadro NVS 110M), and the error report is different.

[Sebastian Heinlein (glatzor)]

The website that you have pointed me at speacks about an Intel GMA950 primarly.

Do you use the open source driver? please append your xorg.conf. Cheers.

[Justin Dugger (jldugger)]

Indeed, the wiki page mentions intel (I wrote that page), but this laptop is an nVidia Quadro NVS 110M. I use the open source nv driver, yes. Attaching xorg.conf.

[Tormod Volden (tormodvolden)]

Can you attach Xorg.9.log as well? (nine not zero)

[David Tomaschik (matir)]

I've experienced the same problem just now:
$ sudo displayconfig-gtk
on_button_test_config_clicked()
xauth: creating new authority file /tmp/guidance.30835/xauthority
Got pid 30848
(0, 0)
displayconfig-gtk: Fatal IO error 104 (Connection reset by peer) on X server :9.0.

Due to bug #132716, I'm temporarily stuck using vesa instead of ati driver, but my graphics card is an ATI Radeon 7500 Mobile. I'm attaching my xorg.conf (post-displayconfig-crash) and will attach Xorg.9.log momentarily.

[Tormod Volden (tormodvolden)]

David, in your case it is because dual-head is not supported by the vesa driver. Of course, displayconfig-gtk should be able to discover this and not make a faulty xorg.conf that will crash the server.

[Thomas Wolfe (tomwolfe)]

I have an ati radeon 9000 mobility and am using the open source ati driver and I too have this problem (not sure why I am not affected by but 132716).

[Thomas Wolfe (tomwolfe)]

I have an ati radeon 9000 mobility and am using the open source ati driver and I too have this problem (not sure why I am not affected by but 132716).

[Tormod Volden (tormodvolden)]

Thomas, it crashes because displayconfig-gtk sets up "zaphod" dual-head which is no longer supported by the ati driver. It should use xrandr. See http://bugs.freedesktop.org/show_bug.cgi?id=12295

Similar issues on intel is seen in bug #137225.

[Sebastian Heinlein (glatzor)]

The problem is that we start a second x server for the test configuration. And this causes problems on some systems. So this is not related to xrandr. AFAIK the xrandr support even for the Intel cards is not yet on a fully working level.

[Tormod Volden (tormodvolden)]

I cannot test on intel, but on ati the test configuration makes the X server crash even if it is the first and only server.

[Bryce Harrington (bryce)]

The "nv" driver supports xrandr for g80 chipsets. I don't know if the NVS 110M falls into this category - wikipedia says it's a g72 core, so perhaps not.

Justin, can you attach your /var/log/Xorg.X.log after the crash? Hopefully it can give a clearer picture of why it failed.

David, since your issue is a separate one (crashing trying to use dual-head with vesa), could you please report it as a separate bug? This bug report will just be focusing on Justin's issue.

[Justin Dugger (jldugger)]

It's been a month, so I decided to retest this (I had moved to nvidia to test out compiz). The same problem occurs, without the S's. Attaching xorg and log shortly.

[be4truth (short-unique-name-in-use)]

Screen and Graphics Preferences - GUI empty (screen shot attached)

I run Hardy 64 bit alpha3 fully updated on an Intel 965 RY mobo. The graphic cards works great. It looks that the #D aspects which were fine in Feisty and broken in Gutsy are back again (stuff like GoogleEarth) works again.

[Dennis Heinson (dheinson)]

I have the same problem: Empty Preferences Applet. However, for me, I cannot activate 3D Effects either.

[Bryce Harrington (bryce)]

Thank you for reporting this bug and for your efforts to make Ubuntu better. As Xorg has improved this past year, an unfortunate side effect of these improvements is that it has rendered several design assumptions in displayconfig-gtk obsolete. So, starting with Hardy we are no longer putting displayconfig-gtk forth as a primary configuration tool, and are putting our development focus into the Screen Resolution applet. As a result, we do not plan to fix this bug and thus are closing it.

For more background on this change, please see this page: [WWW] https://wiki.ubuntu.com/X/DisplayConfigGtk