Comment 6 for bug 35833

Ok... sorry about the time it took me to reply, I just finished re-installing fresh from the new Flight 6 CD, and getting the updates as well as installing the kubuntu-desktop package again. (Last updated packages today: 4/05/2006). I also have been struggling to get a stable wifi connection, since I'm getting the bug with networkmanager concerning the madwifi driver causing uncontrollable disconnects from background scanning. But that's a separate bug... onto this one:

After testing the updated version of the systemsettings display module, I've found it to be much more stable than it was before.
However, while messing around with it, I managed to get it to crash again (lucky me :P). However, luckily, 'administrator mode' still is able to load; it seems to crash only in normal mode, not running as root. I've attached the error output from running kcontrol in a terminal and selecting the display module, as well as the modified version of xorg.conf that playing around in the settings module created.

At first, I tried setting up the two displays under 1 video card 'device', which resulted in the very large desktop, too large to fit on screen, moving the mouse to the edge for scrolling.
After this setup, I was still able to load the module without it crashing!
So, I modified it again and set it up to use 2 'devices' each with a separate display under them. With this setup, I actually was able to configure my widescreen LCD to be the right resolution! No more huge desktop though, but my other secondary screen isn't getting a signal.
I looked into the xorg.conf and found that even though I selected "ATI Radeon (fglrx)" as both video card devices, it didn't change the "driver" line in xorg.conf to read:
driver "fglrx"
It still is using the "ati" mesa driver, running fglrxinfo gives:
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.4.1)

After this configuration, using the xorg.conf attached in the tar.gz file, the display module doesn't load in non-administrator mode. I am still able to click the administrator mode button and it runs it again successfully.