file-roller crashed with SIGSEGV in g_closure_invoke()

[Muelli]

tried to open a tar.xz file here via the browser http://ftp.gnome.org/pub/GNOME/sources/gnome-themes-standard/3.11/gnome-themes-standard-3.11.2.tar.xz

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: file-roller 3.6.3-1ubuntu4.1
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: amd64
Date: Sat Jan 25 18:26:49 2014
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2013-06-18 (221 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: file-roller /tmp/gnome-themes-standard-3.11.2.tar.xz
SegvAnalysis:
 Segfault happened at: 0x41b390: mov (%rbx),%rsi
 PC (0x0041b390) ok
 source "(%rbx)" (0x0000004c) 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/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke (closure=0xb28480, return_value=0x7fff96b8ee90, n_param_values=2, param_values=0x7fff96b8ef40, invocation_hint=0x7fff96b8eee0) at /build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x7994b0, detail=detail@entry=0, instance=instance@entry=0x8c4040, emission_return=emission_return@entry=0x7fff96b8f010, instance_and_params=instance_and_params@entry=0x7fff96b8ef40) at /build/buildd/glib2.0-2.36.0/./gobject/gsignal.c:3584
 g_signal_emit_valist (instance=0x8c4040, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fff96b8f198) at /build/buildd/glib2.0-2.36.0/./gobject/gsignal.c:3338
Title: file-roller crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software 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.