gvfsd-mtp crashed with SIGSEGV

[Michael Thayer]

This was reported by Apport. I did not notice anything amiss, so I am just passing it on. (Perhaps you should add an option into Apport: "I did not notice anything wrong."

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gvfs-backends 1.34.1-2ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 13 16:56:18 2018
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2017-10-24 (119 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.15 /org/gtk/gvfs/exec_spaw/14
SegvAnalysis:
 Segfault happened at: 0x7f92063935a9: mov 0x18(%rax),%rax
 PC (0x7f92063935a9) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 g_task_return_now (task=0x565512fff9e0 [GTask]) at ../../../../gio/gtask.c:1145
 g_task_return (task=0x565512fff9e0 [GTask], type=<optimized out>) at ../../../../gio/gtask.c:1203
 init_second_async_cb (source_object=<optimized out>, res=<optimized out>, user_data=0x565512fff9e0) at ../../../../gio/gdbusproxy.c:1808
 g_task_return_now (task=0x565512fffab0 [GTask]) at ../../../../gio/gtask.c:1145
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: Upgraded to bionic on 2018-02-06 (14 days ago)
UserGroups: adm cdrom dip 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 #1706097, 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.