file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

Bug #479071 reported by fredthefrenchy on 2009-11-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)

Bug Description

Binary package hint: file-roller

I retry with the same file and it was ok.

I think it's a non reproducable bug.

ProblemType: Crash
Architecture: amd64
Date: Mon Nov 9 11:59:29 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/file-roller
NonfreeKernelModules: nvidia
Package: file-roller 2.28.1-0ubuntu1
ProcCmdline: file-roller /home/segardf/Bureau/h264tobox-1.2.5.tar.gz
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
 Segfault happened at: 0x41aa90: mov 0x0(%rbp),%rsi
 PC (0x0041aa90) ok
 source "0x0(%rbp)" (0x0000008d) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
 ?? ()
 _gtk_marshal_BOOLEAN__BOXED (closure=0xefc110,
 IA__g_closure_invoke (closure=0xefc110,
 signal_emit_unlocked_R (node=0xda27a0,
 IA__g_signal_emit_valist (instance=0xdca090,
Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
Uname: Linux 2.6.31-14-generic x86_64

StacktraceTop:egg_tree_multi_drag_button_release_event (widget=0xdca090,
?? () from /usr/lib/
g_closure_invoke ()
?? () from /usr/lib/
g_signal_emit_valist ()

Changed in file-roller (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
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.

Changed in file-roller (Ubuntu):
status: New → Invalid
visibility: private → public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers