Ubuntu
kde-guidance package

[apport] displayconfig-restore.py crashed with SIGSEGV

Bug #104593 reported by Donald Allwright
6
Affects Status Importance Assigned to Milestone
kde-guidance (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Binary package hint: kde-guidance

I had just (successfully) configured my PC with dual monitors for the first time, primary graphics card an NVIDIA GeForce4 MX 4000 card running the nv driver module at 1280*1024, the second an old s3ViRGE card which had been automatically configured to use the s3virge driver at 1024*768 when using the automated guidance configuration tool. However I was then unable to re-use this tool to make any further adjustments. The crash is fully repeatable.

ProblemType: Crash
Architecture: i386
Date: Sun Apr 8 23:59:40 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-0ubuntu3
PackageArchitecture: i386
ProcCmdline: /usr/bin/python /usr/bin/displayconfig-restore
ProcCwd: /home/donald
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
Signal: 11
SourcePackage: kde-guidance
StacktraceTop:
 ?? () from /usr/lib/libXrandr.so.2
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libX11.so.6
Uname: Linux ubuntu 2.6.20-14-lowlatency #2 SMP PREEMPT Mon Apr 2 20:41:03 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Donald Allwright (donald-allwright) wrote :
Laur Mõtus (vprints)
Changed in kde-guidance:
status: Unconfirmed → Confirmed
Revision history for this message
Sebastian Kügler (sebasje) wrote :

Can you run 'displayconfig' from a console and post the output here?

Revision history for this message
Matej Kenda (matejken) wrote :

This has happend with fglrx driver as well. This is happening to me after setting up dual-head display with Xinerama. By using big desktop the problem is not reproducible.

$ uname -a
Linux mk 2.6.20-14-generic #2 SMP Thu Apr 12 22:53:19 UTC 2007 i686 GNU/Linux

$ dpkg -s kde-guidance | grep Version
Version: 0.8.0-0ubuntu4

Output of displayconfig:

$ displayconfig
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
KCrash: Application 'displayconfig' crashing...

Full stack trace attached.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Setting to high because of the continuing stream of apparent duplicates.

Changed in kde-guidance:
importance: Undecided → High
Revision history for this message
Amy (deathkitten) wrote :

I had been also having problems with kde-guidance-powermanager crashing at login like displayconfig-restore.py, and since I am using a desktop instead of a laptop, I tried uninstalling it. When I did this, bug report stuff generated for me by the apport program was slightly different, and this bug report wasn't coming up through the search that comes up before letting one file their bug report. Once I installed that again, it's still crashing, but my error has gone back to being the same as listed in this bug report.

Does anyone know if the power manager problems are related to this? When I'd had it uninstalled, what I'd been reading in bug reports suggested that the problem would go away if I reinstalled the power manager, but that didn't fix it. Also, while searching other bug reports, I found one that looks similar which it has been assigned to someone to work on but has a lower priority than this one, <a href="https://bugs.launchpad.net/ubuntu/+source/kde-guidance/+bug/89663">bug #89663</a>.

My duplicate bug report is #108387, and if there is any other information I can provide to help, please let me know.

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:XRRGetScreenInfo (dpy=0x82a44f0, window=119) at ../../src/XrrConfig.c:351
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Brian Murray (brian-murray) wrote :

I am marking this as a duplicate of 91545 based off the fact that is has more duplicates and will update it's priority to high.

Revision history for this message
Brian Murray (brian-murray) wrote :

Well, it seems all this bug'ss duplicates would have to moved to dupes of 91545 and I'm not in a position to do that right now. However 91545 should be the "master" bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.