gvfsd-trash crashed with SIGABRT in raise()

[Jean-Baptiste Lallement]

Better trace

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gvfs-daemons 1.19.4+git20140116-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
AssertionMessage: ERROR:trashdir.c:218:trash_dir_watch: assertion failed: (dir->monitor == NULL)
CurrentDesktop: Unity
Date: Tue Jan 21 08:24:58 2014
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
ExecutableTimestamp: 1389865292
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_spaw/1
ProcCwd: /
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x408571 "trashdir.c", line=line@entry=218, func=func@entry=0x408780 <__FUNCTION__.22513> "trash_dir_watch", message=message@entry=0x7f21a8003f10 "assertion failed: (dir->monitor == NULL)") at /build/buildd/glib2.0-2.39.3/./glib/gtestutils.c:2352
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x408571 "trashdir.c", line=line@entry=218, func=func@entry=0x408780 <__FUNCTION__.22513> "trash_dir_watch", expr=expr@entry=0x40857c "dir->monitor == NULL") at /build/buildd/glib2.0-2.39.3/./glib/gtestutils.c:2367
 trash_dir_watch (dir=0x7f21b8005600) at trashdir.c:218
 trash_watcher_watch (watcher=0x7f21b8006030) at trashwatcher.c:297
 trash_backend_get_dir_monitor (backend=0x8ee890, create=create@entry=1) at gvfsbackendtrash.c:80
Title: gvfsd-trash crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to trusty on 2012-01-31 (720 days ago)
UserGroups: adm admin cdrom dialout kvm libvirtd lp lpadmin plugdev sambashare sbuild

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