file-roller crashed with SIGSEGV in g_file_make_directory_with_parents()

[Robert]

crashed when trying to extract a tar.gz by clicking on "extract here" in the context menu.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: file-roller 3.5.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Tue Aug 14 18:32:03 2012
ExecutablePath: /usr/bin/file-roller
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
ProcCmdline: file-roller --extract-here file:///home/username/Downloads/apache-maven-3.0.4-bin.tar.gz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe577c48bf4 <g_file_make_directory_with_parents+260>: cmpl $0x1,0x4(%rax)
 PC (0x7fe577c48bf4) ok
 source "$0x1" ok
 destination "0x4(%rax)" (0x00000004) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 g_file_make_directory_with_parents () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: file-roller crashed with SIGSEGV in g_file_make_directory_with_parents()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors: gnome-session[1975]: WARNING: Session 'ubuntu' runnable check failed: Child process exited with code 1

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