gvfsd-afc crashed with SIGSEGV in g_vfs_job_try()

[Daniele]

Description: Ubuntu precise (development branch)
Release: 12.04

gvfs:
  Installed: 1.10.1-1ubuntu1
  Candidate: 1.10.1-1ubuntu1
  Version table:
 *** 1.10.1-1ubuntu1 0
        500 http://mirror.switch.ch/ftp/mirror/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-backends 1.10.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6
Uname: Linux 3.2.0-6-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Fri Dec 30 01:07:48 2011
Disassembly: => 0x0: Cannot access memory at address 0x0
DuplicateOf: https://bugs.launchpad.net/bugs/908350
ExecutablePath: /usr/lib/gvfs/gvfsd-afc
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
ProcCmdline: /usr/lib/gvfs/gvfsd-afc --spawner :1.1 /org/gtk/gvfs/exec_spaw/4
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_US:en
 LANG=en_US.utf8
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:
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
 g_vfs_job_try () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
 g_vfs_daemon_queue_job () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
Title: gvfsd-afc crashed with SIGSEGV in g_vfs_job_try()
UpgradeStatus: Upgraded to precise on 2011-12-22 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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