file-roller crashed with SIGSEGV in g_closure_invoke()

Bug #640032 reported by tetsuo55 on 2010-09-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)

Bug Description

Binary package hint: file-roller

As i was browsing through the chromium source tarbal the crash occured

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: file-roller 2.31.92-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-21.31-generic
Uname: Linux 2.6.35-21-generic x86_64
Architecture: amd64
Date: Thu Sep 16 00:51:02 2010
ExecutablePath: /usr/bin/file-roller
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcCmdline: file-roller /home/username/Downloads/chromium.r58910.tgz.tar
 PATH=(custom, no user)
 Segfault happened at: 0x41d090: mov 0x0(%rbp),%rsi
 PC (0x0041d090) ok
 source "0x0(%rbp)" (0x0000007a) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
 ?? ()
 ?? () from /usr/lib/
 g_closure_invoke () from /usr/lib/
 ?? () from /usr/lib/
 g_signal_emit_valist () from /usr/lib/
Title: file-roller crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

tetsuo55 (akira146) wrote :

 egg_tree_multi_drag_button_release_event (widget=0x1526230,
 ?? () from /usr/lib/
 g_closure_invoke (closure=0x16aba10,
 signal_emit_unlocked_R (node=0x14a9540,
 g_signal_emit_valist (instance=0x1526230,

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