gvfs-fuse-daemon crashed with SIGSEGV in _g_daemon_vfs_get_async_bus()

[Jean-Baptiste Lallement]

I got this crash on session start. no specific action.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs-fuse 1.9.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
Date: Wed Aug 24 23:25:22 2011
ExecutablePath: /usr/lib/gvfs/gvfs-fuse-daemon
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
ProcCmdline: /usr/lib/gvfs//gvfs-fuse-daemon /var/lib/lightdm/.gvfs
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xd1efa1 <_g_daemon_vfs_get_async_bus+17>: mov 0xc(%eax),%eax
 PC (0x00d1efa1) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 _g_daemon_vfs_get_async_bus () at gdaemonvfs.c:1515
 g_daemon_volume_monitor_init (daemon_monitor=0x9769aa8) at gdaemonvolumemonitor.c:206
 g_type_create_instance (type=158777320) at /build/buildd/glib2.0-2.29.16/./gobject/gtype.c:1885
 g_object_constructor (type=158777320, n_construct_properties=0, construct_params=0x0) at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c:1629
 g_object_newv (object_type=158777320, n_parameters=0, parameters=0x0) at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c:1412
Title: gvfs-fuse-daemon crashed with SIGSEGV in _g_daemon_vfs_get_async_bus()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

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