Description of problem: i tried to connect to an already paired bluetooth headset by moving the connect slider to ON Version-Release number of selected component: bluez-5.14-1.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: btd_service_connecting_complete executable: /usr/libexec/bluetooth/bluetoothd kernel: 3.12.10-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (6 frames) #0 btd_service_connecting_complete at src/service.c:319 #1 discovery_complete at profiles/audio/sink.c:253 #2 finalize_discovery at profiles/audio/avdtp.c:1056 #3 connection_lost at profiles/audio/avdtp.c:1155 #4 avdtp_connect_cb at profiles/audio/avdtp.c:2422 #5 connect_cb at btio/btio.c:232
Created attachment 863640 [details] File: backtrace
Created attachment 863641 [details] File: cgroup
Created attachment 863642 [details] File: core_backtrace
Created attachment 863643 [details] File: dso_list
Created attachment 863644 [details] File: environ
Created attachment 863645 [details] File: exploitable
Created attachment 863646 [details] File: limits
Created attachment 863647 [details] File: maps
Created attachment 863648 [details] File: open_fds
Created attachment 863649 [details] File: proc_pid_status
Created attachment 863650 [details] File: var_log_messages
Another user experienced a similar problem: I might have disconnected a USB bluetooth audio adapter, or bluez just died by itself. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: btd_service_connecting_complete executable: /usr/libexec/bluetooth/bluetoothd kernel: 3.15.8-200.fc20.x86_64 package: bluez-5.18-1.fc20 reason: bluetoothd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Tentei enviar um arquivo do meu celular para o computador via Bluetooth porém a conexão não ocorreu gerando esse erro. No celular apareceu para digitar uma senha e confirmar, porém no PC não havia como efetuar a confirmação da senha digitada no Celular e a conexão obviamente falhava. Na sequência o sistema informou que houve um travamento do Bluetooth. Não sei o motivo da falha na conexão. (Traduzido via Google Translate - Translated by Google Translate) I tried to send a file from my phone to the computer via Bluetooth but the connection was not generating this error. In cell appeared to enter and confirm a password, but on the PC there was no place to confirm the password typed in Cellular and obviously the connection failed. Following the system reported that there was a crash of Bluetooth. I do not know why the connection failed. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: btd_service_connecting_complete executable: /usr/libexec/bluetooth/bluetoothd kernel: 3.15.10-201.fc20.x86_64 package: bluez-5.18-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.