Description of problem: I don't know 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/3 crash_function: _dbus_header_get_byte_order executable: /usr/libexec/gvfsd-obexftp kernel: 3.4.11-1.fc16.x86_64 remote_result: 810623 uid: 1000 var_log_messages: Dec 22 17:04:44 localhost abrt[1564]: Saved core dump of pid 1560 (/usr/libexec/gvfsd-obexftp) to /var/spool/abrt/ccpp-2012-12-22-17:04:43-1560 (18333696 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 _dbus_header_get_byte_order at dbus-marshal-header.c:178 #1 _dbus_header_get_field_basic at dbus-marshal-header.c:1370 #2 dbus_message_get_reply_serial at dbus-message.c:1091 #3 _dbus_connection_queue_received_message_link at dbus-connection.c:501 #4 _dbus_transport_queue_messages at dbus-transport.c:1157 #5 do_reading at dbus-transport-socket.c:851 #7 socket_do_iteration at dbus-transport-socket.c:1162 #8 _dbus_transport_do_iteration at dbus-transport.c:976 #9 _dbus_connection_do_iteration_unlocked at dbus-connection.c:1234 #10 _dbus_connection_block_pending_call at dbus-connection.c:2415
Created attachment 667856 [details] File: backtrace
Created attachment 667857 [details] File: cgroup
Created attachment 667858 [details] File: core_backtrace
Created attachment 667859 [details] File: dso_list
Created attachment 667860 [details] File: environ
Created attachment 667861 [details] File: limits
Created attachment 667862 [details] File: maps
Created attachment 667863 [details] File: open_fds
Created attachment 667864 [details] File: proc_pid_status
I tried to browse a Bluetooth device using Blueman. backtrace_rating: 4 Package: gvfs-obexftp-1.14.2-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
I can't see my phone.... backtrace_rating: 4 Package: gvfs-obexftp-1.14.2-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
I was trying to send some pictures from my Nokia phone to my laptop backtrace_rating: 4 Package: gvfs-obexftp-1.14.2-3.fc18 OS Release: Fedora release 18 (Spherical Cow)
Same problem here, can't browse Nokia e71 phone over bluetooth.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Was trying to browse my phone via Bluetooth.
Tried to transfer files from Samsung SIII to F18 reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.3 /org/gtk/gvfs/exec_spaw/9 crash_function: _dbus_header_get_byte_order executable: /usr/libexec/gvfsd-obexftp kernel: 3.9.6-200.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
SIGSEG happening 100% times when trying connect from Gnme Shell via Blootooth to Nokia phone to browse files. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.3 /org/gtk/gvfs/exec_spaw/9 crash_function: _dbus_header_get_byte_order executable: /usr/libexec/gvfsd-obexftp kernel: 3.9.6-200.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 happens always when I try to browse a Nokia E5 using bluetooth reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.3 /org/gtk/gvfs/exec_spaw/1 crash_function: _dbus_header_get_byte_order executable: /usr/libexec/gvfsd-obexftp kernel: 3.10.9-100.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.