Description of problem: [Fedora 18] I got this error when I tried to send a file to my cell phone. Transfer failed. Version-Release number of selected component: gvfs-obexftp-1.14.2-2.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.3 /org/gtk/gvfs/exec_spaw/2 crash_function: link_before executable: /usr/libexec/gvfsd-obexftp kernel: 3.7.2-201.fc18.x86_64 remote_result: 836341 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 link_before at dbus-list.c:120 #1 _dbus_list_prepend_link at dbus-list.c:325 #2 _dbus_list_append_link at dbus-list.c:307 #3 _dbus_message_add_counter_link at dbus-message.c:304 #4 _dbus_message_add_counter at dbus-message.c:338 #5 _dbus_transport_queue_messages at dbus-transport.c:1140 #6 _dbus_connection_get_dispatch_status_unlocked at dbus-connection.c:4211 #7 dbus_connection_get_dispatch_status at dbus-connection.c:4342 #8 message_queue_prepare at dbus-gmain.c:71 #9 g_main_context_prepare at gmain.c:2986
Created attachment 682855 [details] File: backtrace
Created attachment 682856 [details] File: cgroup
Created attachment 682857 [details] File: core_backtrace
Created attachment 682858 [details] File: dso_list
Created attachment 682859 [details] File: environ
Created attachment 682860 [details] File: limits
Created attachment 682861 [details] File: maps
Created attachment 682862 [details] File: open_fds
Created attachment 682863 [details] File: proc_pid_status
Created attachment 682864 [details] File: var_log_messages
I try to access some files on my phone via bluetooth, start blueman-manager, search device, pair it, at this time crashes blueman-assistant (see https://bugzilla.redhat.com/show_bug.cgi?id=923624), than crashes gvfs backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.3 /org/gtk/gvfs/exec_spaw/2 crash_function: link_before executable: /usr/libexec/gvfsd-obexftp kernel: 3.8.4-202.fc18.x86_64 package: gvfs-obexftp-1.14.2-3.fc18 reason: Process /usr/libexec/gvfsd-obexftp was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1
Try to browse files on my cellular phone via bluetooth backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.3 /org/gtk/gvfs/exec_spaw/4 crash_function: link_before executable: /usr/libexec/gvfsd-obexftp kernel: 3.8.4-202.fc18.x86_64 package: gvfs-obexftp-1.14.2-3.fc18 reason: Process /usr/libexec/gvfsd-obexftp was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 2
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.