software-properties-kde crashed with SIGSEGV

Bug #132489 reported by Laur Mõtus
72
This bug affects 2 people
Affects Status Importance Assigned to Milestone
software-properties (Ubuntu)
Invalid
Low
Unassigned

Bug Description

From apport notice.

ProblemType: Crash
Architecture: i386
Date: Tue Aug 14 14:41:54 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/software-properties-kde
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: cdrom
Package: software-properties-kde 0.60
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-properties-kde
ProcCwd: /home/kasutaja
ProcEnviron:
 PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: software-properties
Stacktrace:
 #0 0xb69f4657 in ?? () from /usr/lib/libQtGui.so.4
 #1 0xbf9c1e10 in ?? ()
 #2 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /usr/lib/libQtGui.so.4
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 6136):
 #0 0xb69f4657 in ?? () from /usr/lib/libQtGui.so.4
 #1 0xbf9c1e10 in ?? ()
 #2 0x00000000 in ?? ()
Title: software-properties-kde crashed with SIGSEGV
Uname: Linux kasutaja-laptop 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux
UserGroups:

Revision history for this message
Laur Mõtus (vprints) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_start () from /lib/ld-linux.so.2
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in software-properties:
importance: Undecided → Medium
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this crash reproducible? Apport failed to retrace the stacktrace, and without it we can't properly handle the bug.
Thanks for taking the time to report it, though.

Changed in software-properties:
importance: Medium → Low
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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