[apport] guidance-power-manager.py crashed with SIGSEGV in _PyString_Eq()

Bug #95478 reported by Andre Eisvogel
4
Affects Status Importance Assigned to Milestone
kde-guidance (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kde-guidance

58390 is mayby the same problem?

ProblemType: Crash
Architecture: i386
Date: Sat Mar 24 14:42:47 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/share/python-support/kde-guidance/guidance-power-manager.py
InterpreterPath: /usr/bin/python2.5
Package: kde-guidance-powermanager 0.7.1~svn20070205-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/bin/python /usr/share/python-support/kde-guidance/guidance-power-manager.py
ProcCwd: /home/melanieeisvogel
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kde-guidance
StacktraceTop:
 _PyString_Eq ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux melanieeisvogel-desktop 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i586 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Andre Eisvogel (andre-eisvogel) wrote :
Changed in kde-guidance:
importance: Undecided → Medium
Revision history for this message
baskitcaise (baskitcaise) wrote :

Not sure if this is correct yet, but I had that problem this morning after upgrading from edgy, looking at the xorg.conf showed it was completely rubbish with extra entries all over the shop.

I tried editing by hand but it still seemed to get trashed after startup ( laptop with a 21" monitor connected in clone mode ) either the mouse cursor stayed on one desktop or the monitor went into letterbox so I replaced xorg.conf with a known good one from another distro ( Suse 10.2 ) and all seems to be working at the moment however I have not put it under stress yet, even my synaptic pad applet has stopped throwing errors about shared memory now.

HTH

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This report is so old that I'm sure that this same crash can't happen in Intrepid with the latest guidance-power-manager, especially with the port to PyQt4/KDE4.

Changed in kde-guidance:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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