Version-Release number of selected component: bluez-5.10-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: finalize_discovery executable: /usr/libexec/bluetooth/bluetoothd kernel: 3.11.7-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (3 frames) #1 finalize_discovery at profiles/audio/avdtp.c:1059 #2 connection_lost at profiles/audio/avdtp.c:1158 #3 disconnect_timeout at profiles/audio/avdtp.c:1193
Created attachment 822455 [details] File: backtrace
Created attachment 822456 [details] File: cgroup
Created attachment 822457 [details] File: core_backtrace
Created attachment 822458 [details] File: dso_list
Created attachment 822459 [details] File: environ
Created attachment 822460 [details] File: exploitable
Created attachment 822461 [details] File: limits
Created attachment 822462 [details] File: maps
Created attachment 822463 [details] File: open_fds
Created attachment 822464 [details] File: proc_pid_status
Created attachment 822465 [details] File: var_log_messages
Another user experienced a similar problem: I'm trying to add a device. It worked recently, but now I'm having problems. Also when I bring up the KDE control module to "Manage Bluetooth Devices", I get a nice alert that indicates "Bluetooth is not completely enabled", and a "Fix it" button. Clicking this just makes the alert go away, but it re-appears the next time I bring up the control module. Strangeness. reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: finalize_discovery executable: /usr/libexec/bluetooth/bluetoothd kernel: 3.13.9-200.fc20.x86_64 package: bluez-5.17-1.fc20 reason: bluetoothd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.