file-roller crashed with SIGSEGV in gtk_propagate_event()

Bug #459136 reported by Ervis Tusha
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: file-roller

file-roller crashed with SIGSEGV in gtk_propagate_event()

ProblemType: Crash
Architecture: i386
Date: Fri Oct 23 16:31:56 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/file-roller
NonfreeKernelModules: nvidia
Package: file-roller 2.28.1-0ubuntu1
ProcCmdline: file-roller /home/User Name/Desktop/www/lundro.zip
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x42cbc4 <gtk_propagate_event+116>: mov (%edi),%eax
 PC (0x0042cbc4) ok
 source "(%edi)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0
 ?? ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: file-roller crashed with SIGSEGV in gtk_propagate_event()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev root sambashare tape video www-data

Revision history for this message
Ervis Tusha (etusha) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:IA__gtk_propagate_event (widget=0x9a95128, event=0x4)
?? ()
_gtk_marshal_BOOLEAN__BOXED (closure=0x9bea3c8,
g_closure_invoke () 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 file-roller (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

visibility: private → public
Changed in file-roller (Ubuntu):
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.