New comment by dwhughes on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1437556594

Comment:
A few days ago my Bluetooth headphones stopped connecting with the same `br-connection-profile-unavailable` message.

I tried resetting the system state by first removing the device (`remove F8:4E:17:C3:AE:7E` in bluetoothctl), then powering down for half a minute, booting again and re-adding the device via `bluetoothctl`. No change in behaviour.

<details>
<summary>bluetoothctl session transcript (information from other devices elided)</summary>

```
[bluetooth]# scan on
[NEW] Device F8:4E:17:C3:AE:7E WH-1000XM4
[bluetooth]# pair F8:4E:17:C3:AE:7E
Attempting to pair with F8:4E:17:C3:AE:7E
[CHG] Device F8:4E:17:C3:AE:7E Connected: yes
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 00000000-deca-fade-deca-deafdecacaff
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 81c2e72a-0591-443e-a1ff-05f988593351
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 8901dfa8-5c7e-4d8f-9f0c-c2b70683f5f0
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 931c7e8a-540f-4686-b798-e8df0a2ad9f7
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 96cc203e-5068-46ad-b32d-e316f5e069ba
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: b9b213ce-eeab-49e4-8fd9-aa478ed1b26b
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: f8d1fbe4-7966-4334-8024-ff96c9330e15
[CHG] Device F8:4E:17:C3:AE:7E ServicesResolved: yes
[CHG] Device F8:4E:17:C3:AE:7E Paired: yes
Pairing successful
[CHG] Device F8:4E:17:C3:AE:7E ServicesResolved: no
[CHG] Device F8:4E:17:C3:AE:7E Connected: no
[bluetooth]# trust F8:4E:17:C3:AE:7E
[CHG] Device F8:4E:17:C3:AE:7E Trusted: yes
Changing F8:4E:17:C3:AE:7E trust succeeded
[bluetooth]# connect F8:4E:17:C3:AE:7E
Attempting to connect to F8:4E:17:C3:AE:7E
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
```

</details>

I'm on Ubuntu Jammy, Linux 5.19.0-32-generic (with a heavily personalised SwayWM environment, but I hope that isn't relevant as it worked before and I'm _mostly_ sure I didn't change my environment).

**Package versions and recent changes:**

* bluez: 5.64-0ubuntu1
* pipewire: 0.3.48-1ubuntu3
* libspa*bluetooth: _not installed_

The absence of `libspa-0.2-bluetooth` etc. is presumably irrelevant as my system worked fine without it before.

I checked my `apt` history (`grep -e blue -e pipewire /var/log/apt/history.log`) and I see only one Pipewire- or Bluetooth-related change. Four days ago, I ran `apt install wireplumber` (I forget why) and this changed some packages:

```
Install: pipewire-pulse:amd64 (0.3.48-1ubuntu3, automatic), wireplumber:amd64 (0.4.8-4), libwireplumber-0.4-0:amd64 (0.4.8-4, automatic)
Remove: pipewire-media-session:amd64 (0.4.1-2ubuntu1)
```

I have tried to reverse this by running `apt install pipewire-media-session` (which forces uninstall of wireplumber) and re-running the powercycle-scan-pair-connect recipe above. No improvement.

**Other details:**

Kernel dmesg records no Bluetooth-related messages during the pairing/connection attempt.

`bluetooth.service` systemd journal says:

```
Feb 20 21:43:13 skierfe systemd[1]: Started Bluetooth service.
Feb 20 21:43:13 skierfe bluetoothd[1481]: Starting SDP server
Feb 20 21:43:13 skierfe bluetoothd[1481]: Bluetooth management interface 1.22 initialized
Feb 20 21:44:29 skierfe bluetoothd[1481]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for F8:4E:17:C3:AE:7E: Protocol not available
```

There are a lot of suggested fixes in this thread which seem unlikely to be effective (e.g. "install libspa-bluetooth", when my `apt` history shows that it wasn't installed previously). I would be grateful for advice on which tests to prioritise before I start confusing things with arbitrary changes.

I would _really really love_ if this behaviour could be made more transparent for an "average geek" user. The inscrutability of this error makes it difficult for someone like me, with some geek-fu but mediocre Bluetooth knowledge, to get traction on the issue.