computer-janitor-gtk crashed with SIGSEGV in g_closure_invoke()

Bug #445898 reported by Nawaf Alsallami
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

Removing some old softwares when the crash occurred.

ProblemType: Crash
Architecture: i386
Date: Wed Oct 7 18:33:16 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:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0x2a20937: mov (%edx),%eax
 PC (0x02a20937) ok
 source "(%edx)" (0x0000021a) 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/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: computer-janitor-gtk crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-11-generic i686
UserGroups:

Revision history for this message
Nawaf Alsallami (nawaf) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:gtk_tree_view_bin_expose (widget=<value optimized out>,
gtk_tree_view_expose (widget=0x9f98130, event=0xbf8425d8)
_gtk_marshal_BOOLEAN__BOXED (closure=0x9f62ec8,
?? () from /usr/lib/libgobject-2.0.so.0
?? () 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.