Bug 1324773

Summary: [abrt] bluez: avrcp_player_value_rsp(): bluetoothd killed by SIGSEGV
Product: [Fedora] Fedora Reporter: James Hogarth <james.hogarth>
Component: bluezAssignee: Don Zickus <dzickus>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: dwmw2, dzickus, eyusupov, joshua.rich, marcel, mathias.rhbugzilla, pcfe, r, robin.a.meade, robinlee.sysu, shenada
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/be56a4798cbec8d696e4c5afe706657b09f4e64b
Whiteboard: abrt_hash:04ee4814e59bee7b8f1b6fa619f1fe55c49783c3;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-19 19:28:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description James Hogarth 2016-04-07 09:15:13 UTC 
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
Comment 1 James Hogarth 2016-04-07 09:15:19 UTC 
Created attachment 1144623 [details]
File: backtrace
Comment 2 James Hogarth 2016-04-07 09:15:20 UTC 
Created attachment 1144624 [details]
File: cgroup
Comment 3 James Hogarth 2016-04-07 09:15:22 UTC 
Created attachment 1144625 [details]
File: core_backtrace
Comment 4 James Hogarth 2016-04-07 09:15:23 UTC 
Created attachment 1144626 [details]
File: dso_list
Comment 5 James Hogarth 2016-04-07 09:15:25 UTC 
Created attachment 1144627 [details]
File: environ
Comment 6 James Hogarth 2016-04-07 09:15:26 UTC 
Created attachment 1144628 [details]
File: exploitable
Comment 7 James Hogarth 2016-04-07 09:15:28 UTC 
Created attachment 1144629 [details]
File: limits
Comment 8 James Hogarth 2016-04-07 09:15:29 UTC 
Created attachment 1144630 [details]
File: maps
Comment 9 James Hogarth 2016-04-07 09:15:31 UTC 
Created attachment 1144631 [details]
File: mountinfo
Comment 10 James Hogarth 2016-04-07 09:15:33 UTC 
Created attachment 1144632 [details]
File: namespaces
Comment 11 James Hogarth 2016-04-07 09:15:34 UTC 
Created attachment 1144633 [details]
File: open_fds
Comment 12 James Hogarth 2016-04-07 09:15:36 UTC 
Created attachment 1144634 [details]
File: proc_pid_status
Comment 13 James Hogarth 2016-04-07 09:15:37 UTC 
Created attachment 1144635 [details]
File: var_log_messages
Comment 14 Eldar Yusupov 2016-04-09 14:55:23 UTC 
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
Comment 15 Eldar Yusupov 2016-04-09 14:59:58 UTC 
I could reliably reproduce this problem and applying this patch has fixed it for me.
Comment 16 rh 2016-04-10 21:13:43 UTC 
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
Comment 17 Joshua Rich 2016-04-12 01:42:41 UTC 
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
Comment 18 Dark Shenada 2016-04-12 16:50:29 UTC 
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
Comment 19 Dark Shenada 2016-04-12 17:05:26 UTC 
(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.
Comment 20 mathias.rhbugzilla 2016-04-13 11:45:59 UTC 
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
Comment 21 Eldar Yusupov 2016-06-02 06:25:33 UTC 
Works fine in 5.39
Comment 22 James Hogarth 2016-06-06 15:51:33 UTC 
F24 install this works fine
Comment 23 Don Zickus 2016-09-19 19:28:16 UTC 
Hi,

Closing as it seems the current bluez package has fixed this.

Cheers,
Don