Hide Forgot
Version-Release number of selected component: gvfs-mtp-1.18.3-1.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.9 /org/gtk/gvfs/exec_spaw/2 crash_function: g_hash_table_remove_all_nodes executable: /usr/libexec/gvfsd-mtp kernel: 3.11.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #6 g_hash_table_remove_all_nodes at ghash.c:497 #7 g_hash_table_unref at ghash.c:1026 #8 do_unmount at gvfsbackendmtp.c:754 #9 run at gvfsjobunmount.c:172 #10 g_vfs_job_run at gvfsjob.c:197 #12 g_thread_proxy at gthread.c:798
Created attachment 828348 [details] File: backtrace
Created attachment 828349 [details] File: cgroup
Created attachment 828350 [details] File: core_backtrace
Created attachment 828351 [details] File: dso_list
Created attachment 828352 [details] File: environ
Created attachment 828353 [details] File: limits
Created attachment 828354 [details] File: maps
Created attachment 828355 [details] File: open_fds
Created attachment 828356 [details] File: proc_pid_status
gvfs-1.18.3-2.fc20 claims to fix crashes on unmounts but the fix does not fix this case.
Another user experienced a similar problem: I unplugged an Android phone in MTP mode reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/5 crash_function: g_hash_table_remove_all_nodes executable: /usr/libexec/gvfsd-mtp kernel: 3.14.4-200.fc20.x86_64 package: gvfs-mtp-1.18.3-2.fc20 reason: gvfsd-mtp killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I connected my samsung tablet and created a new folder. During renaming the folder the error occured. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/4 crash_function: g_hash_table_remove_all_nodes executable: /usr/libexec/gvfsd-mtp kernel: 3.14.8-200.fc20.x86_64 package: gvfs-mtp-1.18.3-2.fc20 reason: gvfsd-mtp killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I was installing packages when the error appeared. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/2 crash_function: g_hash_table_remove_all_nodes executable: /usr/libexec/gvfsd-mtp kernel: 3.16.3-200.fc20.x86_64 package: gvfs-mtp-1.18.3-3.fc20 reason: gvfsd-mtp killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.