I believe it was trying to scan a folder on my network.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-backends 1.11.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic-pae 3.2.2
Uname: Linux 3.2.0-12-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sat Feb 4 15:39:37 2012
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.1 /org/gtk/gvfs/exec_spaw/58
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0xb7090373 <g_vfs_job_emit_finished+19>: movzbl 0x14(%eax),%edx
PC (0xb7090373) ok
source "0x14(%eax)" (0x00000014) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
g_vfs_job_emit_finished () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
?? () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
async_ready_callback_wrapper (source_object=0x9e9f078, res=0xb481e220, user_data=0xb4803af0) at /build/buildd/glib2.0-2.31.14/./gio/goutputstream.c:595
g_simple_async_result_complete (simple=0xb481e220) at /build/buildd/glib2.0-2.31.14/./gio/gsimpleasyncresult.c:744
write_async_cb (fd=24, condition=G_IO_OUT, data=0xb480a5b8) at /build/buildd/glib2.0-2.31.14/./gio/gunixoutputstream.c:495
Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_emit_finished()
UpgradeStatus: Upgraded to precise on 2012-02-03 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare vboxusers
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 #838464, 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.