Description:
Bluetooth no longer works as expected following an update applied yesterday on June 30th. Whenever I pair and connect any of my audio devices via Bluetooth using the bluedevil Bluetooth client it appears to connect and change to the newly connected audio device for a time, only to immediately disconnect and reset the bluedevil system tray icon and disconnect from the Bluetooth device whenever I try to actually play any audio.

When checking the logs for the systemd Bluetooth service it appears like some errors appear but nothing too different then the usual error messages that appear when Bluetooth is working. The main unusual thing is the unexpected crashing that is logged whenever I try to play any audio at all. Here is an example:
Jul 01 11:16:51 bluebird systemd[1]: bluetooth.service: Main process exited, code=dumped, status=11/SEGV
Jul 01 11:16:51 bluebird systemd[1]: bluetooth.service: Failed with result 'core-dump'.

I suspected at first that it has to do with an update to the linux-firmware package breaking the functionality of my Bluetooth adapter. But, after downgrading to a previously working version of the linux-firmware package I am still facing the same issue.

I also thought it might be the version of the zen kernel that I am using but after investigating it turns out that the offending update did not update the kernel.

I then tried to fix the problem through downgrading the version of bluez that I was using from version 5.68 to 5.66. This did the trick and it worked perfectly after the downgrade. So it seems as if there is some yet to be fixed bug in bluez that was introduced in version 5.68.


Additional info:
* I am using arch with kde on a wayland session
* I am using the linux-zen kernel
* I am using pipewire with pipewire-media-session for audio
* I am using a Realtek USB Bluetooth adapter with device id: 0bda:2550
* The issue happens with literally any audio source
* I have attached logs from before and after the downgrade from bluez and bluez-libs version 5.68 to 5.66
* I wasn't sure how to submit a bug report to the bluez team so I did not submit an upstream bug report

Steps to reproduce:

Login to a kde session on an arch linux machine with bluez version 5.68 and bluez-libs version 5.68. Set up Bluetooth like normal or make sure it is setup (if it already is) and use the bluedevil Bluetooth client to connect to a Bluetooth audio device. To see the issue play any audio at all after the device is connected and shows up as an audio device. Then, the device should instantly disconnect as the bluetooth daemon appears to crash and restart. This happens again if the attempt to connect the audio device and play audio is repeated.