[apport] displayconfig-restore.py crashed with SIGSEGV

[Pavel Mlčoch]

Binary package hint: kde-guidance

Crash when user login by gdm on remote KDE desktop

ProblemType: Crash
Architecture: i386
Date: Sun Mar 4 04:00:10 2007
DistroRelease: Debian 3.2
ExecutablePath: /usr/share/python-support/kde-guidance/displayconfig-restore.py
InterpreterPath: /usr/bin/python2.5
Package: kde-guidance 0.7.1~svn20070205-0ubuntu1
ProcCmdline: /usr/bin/python /usr/bin/displayconfig-restore
ProcCwd: /home/tata
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kde-guidance
StacktraceTop:
 ?? () from /usr/lib/libXrandr.so.2
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libX11.so.6
Uname: Linux pavka 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux
UserGroups: adm audio cdrom dialout dip fax floppy fuse plugdev scanner tape

[Daniel Holbach (dholbach)]

Thanks for your bug report.

[Ivan Rancati (ivan-sharpmind)]

I've also experienced this problem

[JW (arch0njw)]

I have also experienced this problem.

[Rich S. (rws265)]

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1210190144 (LWP 6601)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb68db454 in ?? () from /usr/lib/libXrandr.so.2
#7 0x0001fcb9 in ?? ()
#8 0x08598348 in ?? ()
#9 0x00000048 in ?? ()
#10 0xb6bb2b2c in ?? () from /usr/lib/libX11.so.6
#11 0x00000000 in ?? ()

[Jesper Skytte (greew)]

I just started using Big Desktop instead of dual X screens - after this, the Power Manager crashes at every login