gvfsd-network crashed with SIGSEGV in g_vfs_monitor_emit_event()

[jsjohnms]

I am having trouble connecting to a Samba share using the file manager. Sometimes it works and other times it does not. The Samba server is on a FreeNas 8.3 box.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.14.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic x86_64
ApportVersion: 2.8-0ubuntu1
Architecture: amd64
Date: Sun Jan 13 12:32:19 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-network
InstallationDate: Installed on 2013-01-01 (12 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121228)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-network --spawner :1.7 /org/gtk/gvfs/exec_spaw/4
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f8941825470 <g_vfs_monitor_emit_event+32>: mov 0x20(%rax),%rbp
 PC (0x7f8941825470) ok
 source "0x20(%rax)" (0x100000022) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_vfs_monitor_emit_event () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? ()
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gvfsd-network crashed with SIGSEGV in g_vfs_monitor_emit_event()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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