Version-Release number of selected component: gvfs-afc-1.24.1-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-afc --spawner :1.2 /org/gtk/gvfs/exec_spaw/0 crash_function: unregister_mount_got_proxy_cb executable: /usr/libexec/gvfsd-afc global_pid: 3093 kernel: 4.0.4-303.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 unregister_mount_got_proxy_cb at gvfsbackend.c:766 #1 g_simple_async_result_complete at gsimpleasyncresult.c:763 #2 complete_in_idle_cb at gsimpleasyncresult.c:775 #7 daemon_main at daemon-main.c:405
Created attachment 1040100 [details] File: backtrace
Created attachment 1040101 [details] File: cgroup
Created attachment 1040102 [details] File: core_backtrace
Created attachment 1040103 [details] File: dso_list
Created attachment 1040104 [details] File: environ
Created attachment 1040105 [details] File: limits
Created attachment 1040106 [details] File: maps
Created attachment 1040107 [details] File: mountinfo
Created attachment 1040108 [details] File: namespaces
Created attachment 1040109 [details] File: open_fds
Created attachment 1040110 [details] File: proc_pid_status
Created attachment 1040111 [details] File: var_log_messages
Thanks for your bugreport. Could you provide more info how this crash happened? Are you able to reproduce the crash? It seems to me it might happen when you hard unplug the device immediately after you pressed unmount in Nautilus, can you prove it?
Can this please be deleted