file-roller crashed with SIGSEGV in g_closure_invoke()

[Andrey Voronov]

Binary package hint: file-roller

Simple open tar.bz2

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: file-roller 2.32.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Mar 9 20:21:41 2011
ExecutablePath: /usr/bin/file-roller
ProcCmdline: file-roller /home/username/Downloads/gitg-0.2.0.tar.bz2
ProcEnviron:
 LANGUAGE=ru_UA:en
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x41d770: mov 0x0(%rbp),%rsi
 PC (0x0041d770) ok
 source "0x0(%rbp)" (0x00000082) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 ?? () 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
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: file-roller crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to natty on 2011-03-04 (4 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare sbuild vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #723841, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.