[apport] apport-checkreports crashed with SIGSEGV

Bug #95799 reported by Sascha Morr
8
Affects Status Importance Assigned to Milestone
python2.5 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: apport

After the last Update and reboot i get this error message:

apport-checkreports crashed with SIGSEGV

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Mar 25 09:03:02 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/share/apport/apport-checkreports
InterpreterPath: /usr/bin/python2.5
Package: apport 0.69
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-checkreports
ProcCwd: /home/sascha
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: apport
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux workstation 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Sascha Morr (saschamorr) wrote :
Revision history for this message
Freddy Martinez (freddymartinez9) wrote :

Thank you for your bug report

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

StacktraceTop:func_traverse (f=0xb7d9a2cc, visit=0x80eea10 <visit_decref>, arg=0x0) at ../Objects/funcobject.c:471
collect (generation=0) at ../Modules/gcmodule.c:295
_PyObject_GC_NewVar (tp=0x8147ba0, nitems=3) at ../Modules/gcmodule.c:897
PyTuple_New (size=3) at ../Objects/tupleobject.c:68

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

unreproducible for me.

Changed in python2.5:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for python2.5 (Ubuntu) because there has been no activity for 60 days.]

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.