gvfsd-smb crashed with SIGSEGV in g_simple_async_result_complete()

[Bryson]

Binary package hint: gvfs

Occurred while using Rythmbox. I am sure it is associated w/ the the gvfs mount issue where I cannot mount a network drive. "Error: DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered Please select another viewer and try again." I can access my shared files but they show up a missing files in Rhythmbox. I have been forcing the .gvfs to load my shared files in Nautilus by opening Rhythmbox and then opening the folder in Nautilus. If open Nautilus before RhythmboxI cannot access the shared files.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
NonfreeKernelModules: nvidia
Package: gvfs-backends 0.99.6-0ubuntu3
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.13 /org/gtk/gvfs/exec_spaw/5
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgio-2.0.so.0
 g_simple_async_result_complete ()
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
Title: gvfsd-smb crashed with SIGSEGV in g_simple_async_result_complete()
Uname: Linux 2.6.27-2-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse pulse-access sambashare scanner users vboxusers video

[Apport retracing service (apport)]

StacktraceTop:command_read_cb (source_object=0x849ea78, res=0x841cc60, user_data=0x8588a50) at gvfschannel.c:480
async_ready_callback_wrapper (source_object=0x849ea78, res=0x841cc60, user_data=0x8588a50)
IA__g_simple_async_result_complete (simple=0x841cc60)
read_async_cb (data=0xb6715078, condition=17, fd=19) at /build/buildd/glib2.0-2.18.0/gio/gunixinputstream.c:319
fd_source_dispatch (source=0xb672c678, callback=0xb7b97ee0 <read_async_cb>, user_data=0xb6715078)

[Sebastien Bacher (seb128)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=551344