Hide Forgot
Description of problem: Attempted to connect bluetooth headset and when setting the input to the headeset it crashed and then bluetooth settings would no longer display and devices and claimed it was bastian's computer Version-Release number of selected component: bluez-5.38-1.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: avrcp_player_value_rsp executable: /usr/libexec/bluetooth/bluetoothd global_pid: 1195 kernel: 4.4.6-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (3 frames) #0 avrcp_player_value_rsp at profiles/audio/avrcp.c:2150 #1 control_response at profiles/audio/avctp.c:831 #2 session_cb at profiles/audio/avctp.c:996
Created attachment 1144623 [details] File: backtrace
Created attachment 1144624 [details] File: cgroup
Created attachment 1144625 [details] File: core_backtrace
Created attachment 1144626 [details] File: dso_list
Created attachment 1144627 [details] File: environ
Created attachment 1144628 [details] File: exploitable
Created attachment 1144629 [details] File: limits
Created attachment 1144630 [details] File: maps
Created attachment 1144631 [details] File: mountinfo
Created attachment 1144632 [details] File: namespaces
Created attachment 1144633 [details] File: open_fds
Created attachment 1144634 [details] File: proc_pid_status
Created attachment 1144635 [details] File: var_log_messages
I had the same problem. Looks like this is a regression fixed in this commit: http://git.kernel.org/cgit/bluetooth/bluez.git/commit/?id=177d27c8c3db4588ec13dae0368f240902c42825
I could reliably reproduce this problem and applying this patch has fixed it for me.
Similar problem has been detected: 1. Attached USB bluetooth adapter 2. Tried to connect to BT headphones using bluetoothctl reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: avrcp_player_value_rsp executable: /usr/libexec/bluetooth/bluetoothd global_pid: 452 kernel: 4.4.6-301.fc23.x86_64 package: bluez-5.38-1.fc23 reason: bluetoothd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: This started happening with the latest kernel. I can no longer use my BT headphones. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: avrcp_player_value_rsp executable: /usr/libexec/bluetooth/bluetoothd global_pid: 21279 kernel: 4.4.6-300.fc23.x86_64 package: bluez-5.38-1.fc23 reason: bluetoothd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: While connected to JBL Pulse BT speaker reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: avrcp_player_value_rsp executable: /usr/libexec/bluetooth/bluetoothd global_pid: 4223 kernel: 4.4.6-301.fc23.x86_64 package: bluez-5.38-1.fc23 reason: bluetoothd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
(In reply to Dark Shenada from comment #18) > Similar problem has been detected: > > While connected to JBL Pulse BT speaker > > reporter: libreport-2.6.4 > backtrace_rating: 4 > cmdline: /usr/libexec/bluetooth/bluetoothd > crash_function: avrcp_player_value_rsp > executable: /usr/libexec/bluetooth/bluetoothd > global_pid: 4223 > kernel: 4.4.6-301.fc23.x86_64 > package: bluez-5.38-1.fc23 > reason: bluetoothd killed by SIGSEGV > runlevel: N 5 > type: CCpp > uid: 0 kill /usr/libexec/bluetooth/obexd then restart bluetoothd could workaround this problem in ~90% chance on my system.
Similar problem has been detected: Try to connect & use the mad catz F.R.E.Q.M wireless headset using bluetooth reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/bluetoothd crash_function: avrcp_player_value_rsp executable: /usr/libexec/bluetooth/bluetoothd global_pid: 1028 kernel: 4.4.6-301.fc23.x86_64 package: bluez-5.38-1.fc23 reason: bluetoothd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Works fine in 5.39
F24 install this works fine
Hi, Closing as it seems the current bluez package has fixed this. Cheers, Don