Fix Bluetooth audio refusing to connect with br-connection-profile-unavailable
Symptom
Bluetooth headphones or speaker refuse to connect. bluetoothctl prints Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable, and the journal shows bluetoothd rejecting the audio profile.
Cause
BlueZ hands audio profiles off to whatever media backend has registered with it. With PipeWire installed but not currently running (socket-activated and never woken), no A2DP endpoint is registered, so BlueZ has no profile to connect to.
Fix
Start PipeWire before connecting:
systemctl --user start pipewire.service wireplumber.service pipewire-pulse.service
Make sure pipewire-audio is installed, because it is what provides the Bluetooth audio support:
sudo pacman -S --needed pipewire-audio
Enable the units so this cannot recur:
systemctl --user enable --now pipewire.service wireplumber.service pipewire-pulse.service
Then retry the connection:
bluetoothctl connect XX:XX:XX:XX:XX:XX
Also make sure the old PulseAudio Bluetooth stack is not half-installed alongside:
pacman -Qs pulseaudio
Verify
bluetoothctl info XX:XX:XX:XX:XX:XX shows Connected: yes, and the device appears in wpctl status as a bluez_output.* sink.