Hide Forgot
Created attachment 831946 [details] bluetoothd debug logs Description of problem: Connecting the Motorokr S305 headset crashes bluetoothd. This seems to be due to the fact that the AVCTP session fails to be established between the two devices. AVCTP session is used by the AVRCP profile (remote control). Version-Release number of selected component (if applicable): Bluez 5.9 from Fedora-Live-Desktop-x86_64-20-Beta-5.iso (Test made on a live USB stick.) How reproducible: Easily reproducible. However it might work in some cases/situations (this need to be confirmed). Steps to Reproduce: 1. Pair the headset (settings->bluetooth->"add a device") 2. If not automatically connected, connect the headset (switch on/off) Actual results: bluetoothd crashes. Expected results: bluetoothd doesn't crash. Devices are paired. Devices are connected. In setting->sound->output the headset can be selected. Sound is played in the headset. Remote control buttons on the headset work (play/pause, previous/next, rewind/fast forward). Additional info: While pairing the Samsung S305 you might be asked to enter a PIN code on the headset... This seems to be another bug. In this case, just cancel the operation and repeat the steps from beginning until pairing is successful. If pairing fails repeat the operation but chose the "0000" PIN code option. To get debug logs from bluetoothd I launched it with the command line: /usr/libexec/bluetooth/bluetoothd -n -P mgmtops -d My first analysis is that the AVCTP protocol, required by the AVRCP profile - remote control, fails to be established between the two devices which results in bluetooth not working anymore (the daemon needs to be stopped then launched again). In a working case the AVCTP session should be established and, in the case where it fails bluetoothd shouldn't end in a blocked state. The error messages are (lines 403 and 405 in the debug file): bluetoothd[3044]: Control: Refusing unexpected connect bluetoothd[3044]: connect error: Connection refused (111) Those messages come from avctp.c: avctp_control_confirm() and btio.c: connect_cb() functions. In the debug logs we can see (lines 382-387): bluetoothd[3044]: src/device.c:device_profile_connected() a2dp-sink Success (0) bluetoothd[3044]: src/device.c:device_profile_connected() returning response to :1.102 bluetoothd[3044]: plugins/policy.c:policy_connect() /org/bluez/hci0/dev_00_0D_FD_4B_C9_95 profile avrcp-controller bluetoothd[3044]: src/service.c:change_state() 0x7fae06bf4770: device 00:0D:FD:4B:C9:95 profile avrcp-controller state changed: disconnected -> connecting (0) bluetoothd[3044]: profiles/audio/avrcp.c:avrcp_connect() path /org/bluez/hci0/dev_00_0D_FD_4B_C9_95 bluetoothd[3044]: profiles/audio/avctp.c:avctp_set_state() AVCTP Connecting then (line 402): bluetoothd[3044]: profiles/audio/avctp.c:avctp_confirm_cb() AVCTP: incoming connect from 00:0D:FD:4B:C9:95 These logs make me think that: - the audio sink is OK - there may be a conflict during the establishment of the AVCTP session. In my understanding AVCTP state should be set to "Connecting" only after it receives a connect request from the headset. It looks like both devices are trying to initiate the connection which leads to the error.
Updates on this bug will be reported on the 01.org bug tracker: https://01.org/jira/browse/BZ-9
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.