gvfsd-trash crashed with SIGSEGV in g_slice_alloc()

[Eustachy Motyka]

error

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: gvfs-daemons 1.23.92-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic i686
ApportVersion: 2.16.2-0ubuntu5
Architecture: i386
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 30 23:41:17 2015
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
InstallationDate: Installed on 2014-12-10 (110 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20141209)
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.5 /org/gtk/gvfs/exec_spaw/1
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=pl_PL
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb73bbb12 <g_slice_alloc+114>: mov (%esi),%edx
 PC (0xb73bbb12) ok
 source "(%esi)" (0x0105512a) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_file_monitor_emit_event () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: gvfsd-trash crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom debian-tor dip disk libvirtd 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 #1372387, 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.