You are not logged in.
Now I know this has probably been asked a ton, but I've tried every solution there is, and nothing worked. I've tried:
Reinstalling BlueZ.
Changing ControllerMode to bredr in the bluetooth config.
Downgrading to 5.16 or whatever.
But every time, I get the same error, that being
br-connection-profile-unavaliableIn the logs, it gives out the old
a2dp-sink profile connect failed for XX:XX:XX:XX:XX:XX: Protocol not availableI am on pipewire, so installing pulseaudio-module-bluetooth won't do anything.
There's surely a lot more that I have tried that I do not remember.
So please, give me anything that I could try, because I really don't want to go to the days of the cable.
Last edited by natan (2022-05-22 12:17:09)
Offline
Had the same issue, and since you were the only other person I could found with the same issue I guessed it had to be some custom config.
I had no custom config on /etc but had some on ~/.config
So long story short, in my case the problem was in:
~/.config/wireplumber/bluetooth.lua.d/50-bluez-config
Doing a diff
diff ~/.config/wireplumber/bluetooth.lua.d/50-bluez-config.lua /usr/share/wireplumber/bluetooth.lua.d/50-bluez-config.lua
showed that my version was missing
bluez_monitor.enabled = true
on the very first line.
Adding that line and restarting solved it for me:
systemctl --user restart pipewire pipewire-pulse wireplumber
Then, since I noticed that I actually don't have anything modified on that config, I went ahead and removed the file to avoid issues in the future.
Hope it helps.
Offline
Hm, my system hasn't made that config file.
I'll try reinstalling pipewire, then maybe going to pulseaudio, and if that doesn't work, I'll blame my really old hardware.
Thanks anyways!
Offline
Okay, I installed pulseaudio and it connected immediately.
I have no clue why pipewire didn't work, I'm sure it's because of my hardware limitations.
Sound doesn't work yet, but I'm guessing its a simple fix.
I don't think I can close this myself, but I'll add a [SOLVED] prefix
Offline
For me, the sympton was bluetooth speaker can be found, paired, but instantly dropped down.
In the network manager gui applet I saw it is continously trying to connect for a short time and dropped down immediately.
journalctl -u bluetooth -r showed me:
Sep 24 13:48:50 archlinux bluetoothd[1836]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for <MAC Address>: Protocol not availabe>
Finally I found a thread in another forum and tried the following:
sudo nano /etc/pulse/default.pa
Added the following line to the following section:
### Automatically restore the volume of streams and devices
load-module module-bluez5-discover
So it is look like for me now:
### Automatically restore the volume of streams and devices
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
load-module module-bluez5-discover
And finally restarted everything:
sudo systemctl restart bluetooth
sudo killall pulseaudio
Now everything is working.
----------
After some search I've also found a package on AUR - maybe it can be also useful.
aur/fix-bt-a2dp 0.1-2 (+4 0.00)
Workaround fixing no A2DP when BT headphone reconnects automatically (after being paired)
Offline
An update on my situation:
I reinstalled at some point and the problem came back, I am using Pipewire.
The fix is to just run *anything* which uses audio: firefox, pavucontrol, even just `aplay` in the terminal. In a bluetoothctl session which is running at the same time, tens of lines going along the lines of "[CHG] Controller (my mac) UUIDs: 00001xxx-0000-1000-8000-00805f9b34fb" appear, and bluetooth works.
Last edited by natan (2023-09-25 14:52:39)
Offline