gvfsd-mtp crashed with SIGSEGV in g_vfs_daemon_register_path()

[Carla Sella]

I was mounting and unmounting Samsung S7 on my PC for coping fotos.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 20:55:16 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2017-06-01 (142 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.22 /org/gtk/gvfs/exec_spaw/9
SegvAnalysis:
 Segfault happened at: 0x7f64ccd6d7dc <g_vfs_daemon_register_path+92>: mov 0x30(%rbp),%rdi
 PC (0x7f64ccd6d7dc) ok
 source "0x30(%rbp)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_vfs_daemon_register_path () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 g_vfs_monitor_new () 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
Title: gvfsd-mtp crashed with SIGSEGV in g_vfs_daemon_register_path()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_vfs_daemon_register_path (daemon=0x0, obj_path=0x7f64bc0153c0 "/org/gtk/vfs/daemon/dirmonitor/5", callback=callback@entry=0x7f64ccd71500 <register_path_cb>, user_data=user_data@entry=0x7f64ac0032b0) at gvfsdaemon.c:537
 g_vfs_monitor_new (backend=backend@entry=0x55add6a4b130) at gvfsmonitor.c:269
 do_create_dir_monitor (backend=0x55add6a4b130, job=0x7f64b8015ee0, filename=0x55add6a63b30 "/Card/Android", flags=<optimized out>) at gvfsbackendmtp.c:454
 g_vfs_job_run (job=0x7f64b8015ee0) at gvfsjob.c:197
 job_handler_callback (data=<optimized out>, user_data=<optimized out>) at gvfsdaemon.c:208

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.