Description of problem: segfault at 58 error 4 in bluetoothd when trying to connect to Motorola Moto Stream speakers Version-Release number of selected component (if applicable): bluez-5.38-1.fc23.x86_64 bluez-cups-5.38-1.fc23.x86_64 bluez-libs-5.38-1.fc23.x86_64 Steps to Reproduce: 1.Try to connect Motorola Moto Stream speakers Actual results: ===================================== [21677.531062] Bluetooth: hci0: BCM: chip id 63 [21677.548109] Bluetooth: hci0: BCM20702A [21677.550083] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000 [21678.315077] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1347 [21678.332074] Bluetooth: hci0: Broadcom Bluetooth Device [21709.465839] bluetoothd[19421]: segfault at 58 ip 0000560ab3f5d57e sp 00007ffe42414f90 error 4 in bluetoothd[560ab3f2f000+e5000] ===================================== Additional info: Bluetooth USB dongle: ID 0b05:17cb ASUSTek Computer, Inc. Broadcom BCM20702A0 Bluetooth See also same problem on other distributions: https://bugs.archlinux.org/task/48644 https://github.com/manjaro/packages-extra/issues/63
I just built a rpm using bluez 5.39 sources. It fixes the segfault problem.
I am getting a similar crash as well with a Plantronics Voyager Legend headset: =============================================== [ 639.482256] bluetoothd[1098]: segfault at 58 ip 000055ac3136357e sp 00007ffc91bc8f30 error 4 in bluetoothd[55ac31335000+e5000] =============================================== My friend has a JBL J56BT headset and its also crashing with a similar trace: =============================================== [ 267.273313] bluetoothd[3363]: segfault at 58 ip 000055c19b49257e sp 00007ffd9dafa700 error 4 in bluetoothd[55c19b464000+e5000] ===============================================
Installed bluez 5.39 from updates-testing and it seems to have fixed the issue for both me and my friend. Should this bug be added to the Bodhi listing? Not sure how to do that.
Identical issue here with a Bose SoundLink Mini II, looking forward for the new bluez to come out of testing.
I'm having the exact same issue when connecting with Sennheiser XL Wireless. I am using the ASUS BT400 (Bluetooth USB dongle). Is this issue limited to people using this specific dongle? lsusb lists the same as Didier G reported: ID 0b05:17cb ASUSTek Computer, Inc. Broadcom BCM20702A0 Bluetooth
Workaround: dnf upgrade bluez --enablerepo=updates-testing
(In reply to Samuel from comment #6) > Workaround: > > dnf upgrade bluez --enablerepo=updates-testing I can confirm that bluez-5.39-1 from updates-testing fixes the issue on my system.
Per user request, closing this CURRENTRELEASE Cheers, Don