Version-Release number of selected component: gvfs-obexftp-1.14.0-1.fc18 Additional info: libreport version: 2.0.17 abrt_version: 2.0.17 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.3 /org/gtk/gvfs/exec_spaw/9 crash_function: _dbus_watch_invalidate kernel: 3.6.2-2.fc18.x86_64 truncated backtrace: :Thread no. 1 (0 frames)
Created attachment 642554 [details] File: core_backtrace
Created attachment 642555 [details] File: environ
Created attachment 642556 [details] File: limits
Created attachment 642557 [details] File: backtrace
Created attachment 642558 [details] File: smolt_data
Created attachment 642559 [details] File: cgroup
Created attachment 642560 [details] File: executable
Created attachment 642561 [details] File: maps
Created attachment 642562 [details] File: dso_list
Created attachment 642563 [details] File: proc_pid_status
Created attachment 642564 [details] File: var_log_messages
Created attachment 642565 [details] File: open_fds
1Pair bluetooth device (cellphone samsung i9000) 2 click to browse external device 3. it crash backtrace_rating: 4 Package: gvfs-obexftp-1.14.2-3.fc18 OS Release: Fedora release 18 (Spherical Cow)
Trying to open obex://[40:98:4E:BF:E9:B6] in thunar backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.3 /org/gtk/gvfs/exec_spaw/5 crash_function: _dbus_watch_invalidate executable: /usr/libexec/gvfsd-obexftp kernel: 3.8.5-201.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
I start Bluetooth Manager and try to browse device, which was unaccessible, and then choose Turn Bluetooth Off on tray icon. After then, gvfsd-obexftp crashes backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.3 /org/gtk/gvfs/exec_spaw/1 crash_function: _dbus_watch_invalidate executable: /usr/libexec/gvfsd-obexftp kernel: 3.8.7-201.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
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Trying to browse files of a Motorola L6 cellphone backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.3 /org/gtk/gvfs/exec_spaw/2 crash_function: _dbus_watch_invalidate executable: /usr/libexec/gvfsd-obexftp kernel: 3.9.2-200.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
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.