gvfsd-mtp crashed with SIGSEGV in g_vfs_job_run()

[Le Gluon Du Net]

don't know what it is about, this bug appeared after I connect my phone on usb connector.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gvfs-backends 1.27.92-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 5 13:39:12 2016
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2013-12-13 (843 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131213)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/0
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fc29cc69370: mov 0x198(%rdx),%r10
 PC (0x7fc29cc69370) ok
 source "0x198(%rdx)" (0x00000198) not located in a known VMA region (needed readable region)!
 destination "%r10" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV in g_vfs_job_run()
UpgradeStatus: Upgraded to xenial on 2015-12-15 (111 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers

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