gvfsd-trash crashed with SIGABRT in g_thread_abort()

[Adam Conrad]

No idea how I triggered this one, but maybe the backtrace will be useful.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gvfs-daemons 1.19.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1
Uname: Linux 3.13.0-7-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 7 18:29:53 2014
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
InstallationDate: Installed on 2012-12-09 (425 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121209)
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.3 /org/gtk/gvfs/exec_spaw/0
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 LANG=en_CA.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 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-trash crashed with SIGABRT in g_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sbuild sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_thread_abort (status=<optimized out>, function=function@entry=0x7fc3a8ae2d8e "pthread_mutex_lock") at /build/buildd/glib2.0-2.39.4/./glib/gthread-posix.c:74
 g_mutex_lock (mutex=<optimized out>) at /build/buildd/glib2.0-2.39.4/./glib/gthread-posix.c:209
 emit_cb (data=0xd3e2d0) at /build/buildd/glib2.0-2.39.4/./gio/gfilemonitor.c:389
 g_main_dispatch (context=0xd0e530) at /build/buildd/glib2.0-2.39.4/./glib/gmain.c:3065
 g_main_context_dispatch (context=context@entry=0xd0e530) at /build/buildd/glib2.0-2.39.4/./glib/gmain.c:3640

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

https://errors.ubuntu.com/problem/fa9afb89115983ae29bf51534d7610aa57c3b289 suggests it's fixed in current versions