[hardy] displayconfig-restore causes X to crash

quite an exotic setup.. Note that nvidia doesn't support randr-1.2 while -ati does.

I'm sorry but configurations with both -fglrx and -nvidia installed is not supported in Hardy and likely won't be supported in Intrepid either. It may be possible to get it working on an individual basis with a lot of hacking, but it's not a feature we will be supporting in the near- or mid-term, so we're marking that task as wontfix.

However, the displayconfig-restore bug with guidance-backends seems relevant and possibly fixable, so leaving that task open.

Bryce,

I'm using the binary nvidia driver and the free radeon driver. I'm re-opening this ticket as your justification for closing it doesn't quite apply.

I agreed with Timo Aaltonen that I need to provide a proper backtrace. I'll do so as soon as time permits.

From a Guidance perspective, I think in order to make this kind of case work it would be necessary to re-engineer this to work with Xrandr 1.2. That kind of invasive change is clearly not suitable for an update to the released version. Using Guidance Display Config is already deprecated in Hardy for Ubuntu. For Kubuntu it is intended to migrate to a KDE4 native tool in Intrepid, so further progress for this is extremely unlikely.

I ran into an identical traceback on my machine after I installed Kubuntu 64-bit Hardy. In my case, however, I made zero customizations to the out-of-the box drivers or xorg.conf, and my sole graphics card is the integrated X200 that comes with ATI's Xpress200 chipset.

Interestingly, there were no errors in xorg.log, only in kdm.log. (Probably related to the fact that I was getting the login screen, but after I logged in, the screen would go black for a few seconds and I would be kicked back out to the login screen.) Failsafe login worked, and once I disabled the executable bit on displayconfig-restore regular login to the default KDE desktop started working too. (Except that my wide-screen Dell monitor is not recognized and the "Monitor and Display" module in the system settings cannot load.)

I have a rather unexotic setup and I don't have non-free drivers installed.

I'm running the RADEON driver. In order to get X to start at all, I have to comment out displayconfig-restore.

If I do that X starts just fine.

If I then run displayconfig-restore, X dies with this trace

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c780e]
1: [0xb7fa7420]
2: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7c037a2]
3: /usr/bin/X [0x81506ee]
4: /usr/bin/X(Dispatch+0x2cf) [0x808d8df]
5: /usr/bin/X(main+0x48b) [0x807471b]
6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d37450]
7: /usr/bin/X(FontFileCompleteXLFD+0x201) [0x8073a91]

I've attached my Xorg.log and will attach xorg.conf next.

I have reopened this because I can reproduce this bug on a box with a default config file and only 1 monitor. This is a regression from 7.10

Seems I can reliably crash X with a few lines of python doing anything with mplayer. Python script attached.

Sorry, that should be "*or* doing anything with mplayer"

That doesn't cause a crash here on an Intel chipset. Mplayer I've had crashing problems with, but I haven't figured it out yet.

I have ran into what I believe is the same problem. I get a similar stack trace:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x94) [0x10092df4]
1: [0x100344]
2: /usr/bin/X(VidModeGetCurrentModeline+0x3c) [0x1009769c]
3: /usr/lib/xorg/modules/extensions//libextmod.so [0xf971c84]
4: /usr/bin/X [0x10135380]
5: /usr/bin/X(Dispatch+0x38c) [0x1004ad4c]
6: /usr/bin/X(main+0x4a4) [0x1002bcc4]
7: /lib/libc.so.6 [0xfb6db10]
8: /lib/libc.so.6 [0xfb6dcd0]

which happens when I run displayconfig-restore. Removing displayconfig-restore enables me to login. Otherwise the X server just crashed during KDE startup (I'm running kubuntu).

I'm running on a PPC Mac Mini. I don't really believe that's relevant, though. The videocard is (from lspci):
0000:00:10.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01)

I'm using the "radeon" X driver.

I didn't have these problems when I installed hardy. But when I did a apt-get dist-upgrade today (for the very first time since installing Hardy, I think) this problem started to appear.

Could someone change this to something other than wishlist as this is impacting at least 2 people with uninteresting hardware that used to work just fine.

[This is an automated message]

Hi laga,

Please attach the output of `lspci -vvnn` too.

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

My setup works again with intrepid, so this bug has been fixed somehow.