gvfsd-mtp crashed with SIGSEGV in g_vfs_job_run()

[Pankaj Kumar Mondal]

This error occurred while I was trying to play a video file.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Apr 8 21:25:17 2018
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2017-12-28 (101 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.4 /org/gtk/gvfs/exec_spaw/7
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_IN:en
 PATH=(custom, user)
 LANG=en_IN
SegvAnalysis:
 Segfault happened at: 0x7f4ed5bef370: mov 0x198(%rdx),%r10
 PC (0x7f4ed5bef370) 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 2018-01-31 (67 days ago)
UserGroups: adm cdrom dialout dip 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 #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.