After enableing second monitor guidance crashes on every startup and graphical display manager crashes immidiately when launched

[Laur Mõtus]

Binary package hint: kde-guidance

After enableing second monitor in KDE control center guidance crashes on every startup and graphical display manager crashes immidiately when launched. It changed the resolutions of both monitors to 640*480, although i only changed the settings for second monitor and set the reso to 1024*768 the first monitor's reso was also 1024*768. It shouldn't even have touched the first monitors reso settings.
I am very open to helping to solve this bug, let's get the nasty mess out..

ProblemType: Crash
Architecture: i386
Date: Mon Apr 9 21:57:38 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/share/python-support/kde-guidance/displayconfig-restore.py
InterpreterPath: /usr/bin/python2.5
Package: kde-guidance 0.8.0-0ubuntu4
PackageArchitecture: i386
ProcCmdline: /usr/bin/python /usr/bin/displayconfig-restore
ProcCwd: /home/laur
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=et_EE.UTF-8
Signal: 11
SourcePackage: kde-guidance
StacktraceTop:
 ?? () from /usr/lib/libXrandr.so.2
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libX11.so.6
Uname: Linux NX6125 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Laur Mõtus (vprints)]

Computer is HP's laptop nx6125
using open ati driver

[Sebastian Kügler (sebasje)]

Can you run "displayconfig" from the commandline and post the output?

[Laur Mõtus (vprints)]

KCrash: Application 'displayconfig' crashing...

attached is the backtrace, but i didn't find the debugging package for that in the repos

[Sebastian Kügler (sebasje)]

Is this really the commandline output from displayconfig? I'm especially interested in a python backtrace, everything else is essentially useless.

[Laur Mõtus (vprints)]

Yes, it really is that short.
Where could i find the bebugging package?

[Sebastian Kügler (sebasje)]

There is no debugging package.

So it crashes without a trace? I cannot do anything about this, I'm afraid.

[Laur Mõtus (vprints)]

Could someone make the debugging package?

Is this
http://librarian.launchpad.net/7237276/out.txt

backtrace useless?

And is python backtrace somewhat different?

[Sebastian Kügler (sebasje)]

There is no 'debugging mode' for guidance, so I suppose it's not easily possible to create something like a debugging package.

Your backtrace is useless, yes. I'd expect a python backtrace showing up on the commandline.

By the way, does running "kcmshell displayconfig" show something in the commandline output?

[Laur Mõtus (vprints)]

laur@NX6125:~$ kcmshell displayconfig
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device

Pythonize constructor -- pid = 5668
Python interpreter initialized!

Pythonize constructor -- pid = 5668
KCrash: Application 'kcmshell' crashing...
laur@NX6125:~$

[Sebastian Kügler (sebasje)]

Not useful, I'm afraid. :/

[dp (dp-de)]

I found this thread searching for info on crashes I experience with every kde start (powermanager) or whenever I try to open the displayconfig control. It behaves just like Laur Motus described it.
This is kubuntu 7.04 on a ASUS A8N-SLI-Premium Bios Rev 1009 with an ASUS EN7600GT grasphic card running on the nvidia driver.

The crashes started only after I had configured the dual monitor setup, the last action of displayconfig seems to have been setting the resolution down to 640x480.
When trying to get some info by running displayconfig or kcmshell displayconfig all I get in the terminal is the trivial:

KCrash: Application 'displayconfig' crashing...

 or

Pythonize constructor -- pid = 8519
Python interpreter initialized!

Pythonize constructor -- pid = 8519
KCrash: Application 'kcmshell' crashing...

[Luka Renko (lure)]

This looks like duplicate of bug 91545.

I have prepared test packages (i386 only) with fix from KDE SVN. You can install and test them:

http://muse.19inch.net/~lure/feisty/kde-guidance_0.8.0-0ubuntu6~lure1_i386.deb
http://muse.19inch.net/~lure/feisty/kde-guidance-powermanager_0.8.0-0ubuntu6~lure1_i386.deb

Please report back if it fixes or not your problem. If we get good feedback, this fix will be considered for https://wiki.ubuntu.com/StableReleaseUpdates

[wonderwind (wonderwind1)]

I may have a workaround.
Try modifying /etc/X11/xorg.conf thusly:

  Add "virtual x_dim y_dim" to SubSection "Display" in Section "screen"

Match x_dim, y_dim to your screen size.
"man xorg.conf" tells you that without the "virtual" statement, the virtual screen size is set to the maximum available under "modes", hence the magnifying-glass-fun.

(Ohhhh, yeah! I've had fun with this one alright. much fumbling with fglrx ati official driver, installing, uninstalling, almost wiping kubuntu, etc. ...tired,,need sleep.. need foood... #(

[wonderwind (wonderwind1)]

Uh, oops, forgot to mention that while the screen works as expected with the "virtual" statement addition, the display control still crashes,, prolly broke something during all the fumbling in the dark, sigh!