Description of problem: When trying to access files on a coupled smartphone. 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/0 crash_function: _wordcopy_fwd_dest_aligned executable: /usr/libexec/gvfsd-obexftp kernel: 3.7.2-204.fc18.x86_64 remote_result: NOTFOUND uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 _wordcopy_fwd_dest_aligned at wordcopy.c:195 #1 memmove at ../string/memmove.c:75 #3 delete at dbus-string.c:1175 #5 _dbus_string_delete at dbus-string.c:1200 #6 load_message at dbus-message.c:4171 #7 _dbus_message_loader_queue_messages at dbus-message.c:4245 #8 _dbus_transport_get_dispatch_status at dbus-transport.c:1101 #9 _dbus_transport_queue_messages at dbus-transport.c:1128 #10 _dbus_connection_get_dispatch_status_unlocked at dbus-connection.c:4211 #11 dbus_connection_send_with_reply at dbus-connection.c:3440
Created attachment 686146 [details] File: backtrace
Created attachment 686147 [details] File: build_ids
Created attachment 686148 [details] File: cgroup
Created attachment 686149 [details] File: core_backtrace
Created attachment 686150 [details] File: dso_list
Created attachment 686151 [details] File: environ
Created attachment 686152 [details] File: limits
Created attachment 686153 [details] File: maps
Created attachment 686154 [details] File: open_fds
Created attachment 686155 [details] File: proc_pid_status
Created attachment 686156 [details] File: smolt_data
Created attachment 686157 [details] File: var_log_messages
Upon connecting using gnome (BT icon on the tile bar) to the phone in order to search files on it. backtrace_rating: 4 Package: gvfs-obexftp-1.14.2-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
Connected to my Mac over bluetooth, and when I went to browse device from the icon in the panel I recieved the error. backtrace_rating: 4 Package: gvfs-obexftp-1.14.2-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Trying to browse file on a Motorola L6 via bluetooth reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.3 /org/gtk/gvfs/exec_spaw/3 crash_function: _wordcopy_fwd_dest_aligned executable: /usr/libexec/gvfsd-obexftp kernel: 3.9.9-201.fc18.x86_64 package: gvfs-obexftp-1.14.2-4.fc18 reason: Process /usr/libexec/gvfsd-obexftp was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
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.