file-roller crashed with SIGSEGV in g_simple_async_result_complete()

[Marcos]

trying to open the file Samopal_by_zlobnoe_belko.gz throws the error

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: file-roller 3.5.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.13-lowlatency 3.5.4
Uname: Linux 3.5.0-15-lowlatency x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 26 09:54:17 2012
ExecutablePath: /usr/bin/file-roller
InstallationMedia: Ubuntu-Studio 12.04 "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: file-roller --extract-here file:///home/username/Escritorio/wireless/Samopal_by_zlobnoe_belko.gz
SegvAnalysis:
 Segfault happened at: 0x419a33: mov 0x20(%rax),%rdi
 PC (0x00419a33) ok
 source "0x20(%rax)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: file-roller crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin aegir audio avahi-autoipd backup cdrom crontab daemon dialout dip disk fax floppy fuse games gnats irc kmem kvm libuuid lightdm list lp lpadmin mail man messagebus mlocate mysql netdev news nopasswdlogin ntp operator pcscd plugdev postdrop postfix proxy pulse pulse-access root rtkit sambashare saned sasl scanner shadow src ssh ssl-cert staff sudo sys syslog tape tty users utempter utmp uucp vboxusers video voice www-data

[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 #1036878, 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.