Ubuntu
kde-guidance package

[apport] displayconfig-restore.py crashed with SIGSEGV

Bug #109362 reported by Sanchola on 2007-04-23

This bug report is a duplicate of: Bug #91545: MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo(). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	kde-guidance (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: kde-guidance

When enabling dual monitor support. Reproduceable with both ati and fglrx

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Apr 23 11:01:59 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-0ubuntu5
PackageArchitecture: i386
ProcCmdline: /usr/bin/python /usr/bin/displayconfig-restore
ProcCwd: /home/esanchez
ProcEnviron:
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
Signal: 11
SourcePackage: kde-guidance
StacktraceTop:
?? () from /usr/lib/libXrandr.so.2
?? ()
?? ()
?? ()
?? () from /usr/lib/libX11.so.6
Uname: Linux Ophelia 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message

Sanchola (sanchola) wrote on 2007-04-23:

Dependencies.txt Edit (5.5 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (822 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (5.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (674 bytes, text/plain; charset="utf-8")
Registers.txt Edit (511 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (198 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (225 bytes, text/plain; charset="utf-8")

Revision history for this message

Richard Birnie (rbirnie-deactivatedaccount) wrote on 2007-04-23:

Sanchola,

thanks for taking the time to report this. I think this is a duplicate of an existing bug. I'll link it to that one and the discussion can be followed there.