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

[Gen X]

1)Description: Ubuntu oneiric (development branch)
Release: 11.10

2) gvfs:
  Instalados: 1.9.3-0ubuntu1
  Candidato: 1.9.3-0ubuntu1
  Tabla de versión:
 *** 1.9.3-0ubuntu1 0
        500 http://mx.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
        100 /var/lib/dpkg/status

3) nothing
4) the program send this error message

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs-fuse 1.9.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Aug 24 02:05:08 2011
ExecutablePath: /usr/lib/gvfs/gvfs-fuse-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110817)
ProcCmdline: /usr/lib/gvfs//gvfs-fuse-daemon /var/lib/lightdm/.gvfs
SegvAnalysis:
 Segfault happened at: 0x7f6adb4a6eb7: mov 0x18(%rax),%rax
 PC (0x7f6adb4a6eb7) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance()
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.