computer-janitor-gtk crashed with SIGSEGV

Bug #449624 reported by Gustavo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
computer-janitor (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: computer-janitor

computer-janitor-gtk crashed with SIGSEGV this thing ''SIGSEGV'' crashed again....!!!!!!!!!

ProblemType: Crash
Architecture: i386
Date: Mon Oct 12 11:30:53 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/computer-janitor-gtk
InterpreterPath: /usr/bin/python2.6
Package: computer-janitor-gtk 1.13.3-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/computer-janitor-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SegvAnalysis:
 Segfault happened at: 0x116aa02: mov 0x4(%edx),%eax
 PC (0x0116aa02) ok
 source "0x4(%edx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: computer-janitor
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: computer-janitor-gtk crashed with SIGSEGV
Uname: Linux 2.6.31-13-generic i686
UserGroups: root

Revision history for this message
Gustavo (gstv.inc) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:_gtk_rbtree_next (tree=0x99f73c8, node=0x0)
gtk_tree_view_bin_expose (widget=<value optimized out>,
gtk_tree_view_expose (widget=0x96b4130, event=0xbf9f6b38)
_gtk_marshal_BOOLEAN__BOXED (closure=0x967f230,
?? () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in computer-janitor (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
to be removed (liw)
visibility: private → public
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.