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

[Edson T. Marques]

Just did the last upgrade and reboot. After login I try the new user menu at top right of the screen and edit Online Accounts, fill seconds after the window appear the system shows this crash.
I'm using gnome-shell. Startup applications are Evolution Alarm Notifier, Cairo Dock, Kopete, NVIDIA X server Settings, Synapse and Sinaptics Touchpad Configuration

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs-fuse 1.9.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Aug 24 15:30:07 2011
ExecutablePath: /usr/lib/gvfs/gvfs-fuse-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
ProcCmdline: /usr/lib/gvfs//gvfs-fuse-daemon /var/lib/lightdm/.gvfs
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f9078ce6eb7: mov 0x18(%rax),%rax
 PC (0x7f9078ce6eb7) 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: Upgraded to oneiric on 2011-08-25 (5 days ago)
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.