Description of problem: plugging in phone via usb Version-Release number of selected component: gvfs-afc-1.22.0-1.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/gvfs-afc-volume-monitor crash_function: plist_copy_node executable: /usr/libexec/gvfs-afc-volume-monitor kernel: 3.16.1-301.mst.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 plist_copy_node at plist.c:194 #5 plist_copy at plist.c:237 #6 lockdownd_do_pair at lockdown.c:959 #7 lockdownd_validate_pair at lockdown.c:1124 #8 lockdownd_client_new_with_handshake at lockdown.c:770 #9 _g_vfs_afc_volume_update_metadata at afcvolume.c:147 #10 g_vfs_afc_volume_new at afcvolume.c:243 #11 g_vfs_afc_monitor_create_volume at afcvolumemonitor.c:40 #12 g_vfs_afc_monitor_idevice_event at afcvolumemonitor.c:94 #13 usbmux_event_cb at idevice.c:136
Created attachment 944901 [details] File: backtrace
Created attachment 944902 [details] File: cgroup
Created attachment 944903 [details] File: core_backtrace
Created attachment 944904 [details] File: dso_list
Created attachment 944905 [details] File: environ
Created attachment 944906 [details] File: limits
Created attachment 944907 [details] File: maps
Created attachment 944908 [details] File: open_fds
Created attachment 944909 [details] File: proc_pid_status
Created attachment 944910 [details] File: var_log_messages
Another user experienced a similar problem: plugging in my phone via usb reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-afc --spawner :1.3 /org/gtk/gvfs/exec_spaw/3 crash_function: plist_copy_node executable: /usr/libexec/gvfsd-afc kernel: 3.16.1-301.mst.fc21.x86_64 package: gvfs-afc-1.22.0-1.fc21 reason: gvfsd-afc killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Thanks for your bugreport. It seems to me like libimobiledevice bug, because there are similar bug reports e.g. for libgpod and upower. I've filed upstream bug for: https://github.com/libimobiledevice/libimobiledevice/issues/163
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.