Segfault when Bluetooth device disappears
Distribution: Arch Linux Pipewire version: 0.3.43-1 Wireplumber version: 0.4.6-1
My machine has a buggy bluetooth adapter. Every half hour, the USB device disappears and immediately reappears again. But until now this was not an issue.
Since updating my machine today, everytime the bluetooth adapter reappears, wireplumber segfaults. This stops all currently running audio output, and is obviously pretty disruptive.
I see the following in dmesg
:
[Thu Jan 13 19:44:02 2022] usb 3-3.2.4.1.4: USB disconnect, device number 22
[Thu Jan 13 19:44:02 2022] usb 3-3.2.4.1.4: new full-speed USB device number 23 using xhci_hcd
[Thu Jan 13 19:44:02 2022] usb 3-3.2.4.1.4: New USB device found, idVendor=0a5c, idProduct=21e8, bcdDevice= 1.12
[Thu Jan 13 19:44:02 2022] usb 3-3.2.4.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Thu Jan 13 19:44:02 2022] usb 3-3.2.4.1.4: Product: BCM920702 Bluetooth 4.0
[Thu Jan 13 19:44:02 2022] usb 3-3.2.4.1.4: Manufacturer: Broadcom Corp
[Thu Jan 13 19:44:02 2022] usb 3-3.2.4.1.4: SerialNumber: [serial redacted]
[Thu Jan 13 19:44:02 2022] Bluetooth: hci0: BCM: chip id 63
[Thu Jan 13 19:44:02 2022] Bluetooth: hci0: BCM: features 0x07
[Thu Jan 13 19:44:02 2022] Bluetooth: hci0: [hostname redacted]
[Thu Jan 13 19:44:02 2022] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1459
[Thu Jan 13 19:44:02 2022] Bluetooth: hci0: BCM20702A1 'brcm/BCM20702A1-0a5c-21e8.hcd' Patch
[Thu Jan 13 19:44:03 2022] Bluetooth: hci0: Broadcom Bluetooth Device
[Thu Jan 13 19:44:03 2022] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1459
[Thu Jan 13 19:44:03 2022] wireplumber[137519]: segfault at 44 ip 00007fd9f432fc37 sp 00007fffe2131c90 error 4 in libspa-bluez5.so[7fd9f4308000+66000]
[Thu Jan 13 19:44:03 2022] Code: 0f 05 00 00 8b 15 e9 e4 05 00 44 8b 74 24 0c 83 fa 03 0f 87 3b 06 00 00 41 f7 d6 44 21 75 00 48 83 7b 28 00 0f 84 3e 01 00 00 <41> 0f b7 45 44 c7 44 24 0c 00 00 00 00 66 83 f8 01 0f 84 12 04 00
The instruction pointer, as well as the hexdump, stay the same for every crash.
I'm not sure how to debug this further, or if this is even the correct place to report.
Can someone help?