gvfsd-archive crashed with SIGSEGV in g_simple_async_result_complete()

[igi]

Binary package hint: gvfs

None.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gvfs-backends 1.6.1-0ubuntu1build1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Wed Jun 2 21:45:21 2010
ExecutablePath: /usr/lib/gvfs/gvfsd-archive
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/lib/gvfs/gvfsd-archive file=/media/Documenti/Scrivania/igi\ 2010_v05_2010-06-02.iso
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8055825: movzbl 0x14(%eax),%edx
 PC (0x08055825) ok
 source "0x14(%eax)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? ()
 g_simple_async_result_complete ()
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
Title: gvfsd-archive crashed with SIGSEGV in g_simple_async_result_complete()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 g_simple_async_result_complete ()
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.