gvfsd-archive crashed with SIGSEGV in g_vfs_job_try()

[userdce]

I tried to mount a Gentoo ISO file and was not able to see where it was mounted so I mounted it again. I unmounted the file and this bug appeared.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs-backends 1.9.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-8.10-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
NonfreeKernelModules: wl fglrx
Architecture: amd64
Date: Tue Aug 9 14:19:09 2011
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/lib/gvfs/gvfsd-archive
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110716)
ProcCmdline: /usr/lib/gvfs/gvfsd-archive file=/home/username/Desktop/livedvd-amd64-multilib-11.2.iso
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 g_vfs_job_try () from /usr/lib/gvfs/libgvfsdaemon.so
 g_vfs_daemon_queue_job () from /usr/lib/gvfs/libgvfsdaemon.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gvfsd-archive crashed with SIGSEGV in g_vfs_job_try()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin mythtv netdev plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 g_vfs_job_try () from /usr/lib/gvfs/libgvfsdaemon.so
 g_vfs_daemon_queue_job () from /usr/lib/gvfs/libgvfsdaemon.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 811049, so it 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.