Hide Forgot
Description of problem: I tried to copy a song with invalid encoding to my nexus 5... Version-Release number of selected component: gvfs-mtp-1.18.3-1.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.5 /org/gtk/gvfs/exec_spaw/4 executable: /usr/libexec/gvfsd-mtp kernel: 3.11.9-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #1 ptp_transaction_new at ptp.c:152 #2 ptp_transaction at ptp.c:400 #3 ptp_getstorageids at ptp.c:596 #4 LIBMTP_Get_Storage at libmtp.c:3960 #5 add_cache_entries_for_filename at gvfsbackendmtp.c:208 #6 get_cache_entry at gvfsbackendmtp.c:269 #7 do_query_info at gvfsbackendmtp.c:1174 #8 g_vfs_job_run at gvfsjob.c:197 #10 g_thread_proxy at gthread.c:798 Potential duplicate: bug 957162
Created attachment 830788 [details] File: backtrace
Created attachment 830789 [details] File: cgroup
Created attachment 830790 [details] File: core_backtrace
Created attachment 830791 [details] File: dso_list
Created attachment 830792 [details] File: environ
Created attachment 830793 [details] File: exploitable
Created attachment 830794 [details] File: limits
Created attachment 830795 [details] File: maps
Created attachment 830796 [details] File: open_fds
Created attachment 830797 [details] File: proc_pid_status
Created attachment 830798 [details] File: var_log_messages
Another user experienced a similar problem: i dont not reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/3 executable: /usr/libexec/gvfsd-mtp kernel: 3.16.7-200.fc20.x86_64 package: gvfs-mtp-1.18.3-3.fc20 reason: gvfsd-mtp killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Thanks for your bugreport. The crash isn't caused by the invalid encoding, but it is caused because new operation on backend is executed after unmount is finished. This was fixed upstream recently, we have to backport patches from: https://bugzilla.gnome.org/show_bug.cgi?id=710986 If you have problems with encoding, please file new bug report with reproduction details...
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.