New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a2dp-sink profile connect failed for X: Protocol not available #348
Comments
@alvarlagerlof this normally happens when there is no endpoint registered, perhaps PulseAudio or Pipewire are not available? |
They are. Pipewire in my case. My external 3.5mm speakers work fine. |
Well it doesn't seem to be registering with bluetoothd, try running bluetoothd manually with sudo /bluetoothd -dn and check what if there is any endpoints being registered. |
|
Looks like there is no endpoints being registered, here is what we expect would happend:
|
Right, I am not sure what that means? Is Bluez or Pipewire or the Headphones at fault? |
Probably something is not right in pipewire, was that updated recently? |
Yes, it has. For sure between the Silverblue versions above. Do I make an issue there instead? |
My issue was in a changed wireplumber config. I reset it to default and everything works now. |
I have tried a bunch of things here but I keep on getting this. I am on 36.20220530.2 of Fedora Silverblue. Version 36.20220512.0 does not have this issue. I don't know where to get more information but I will gladly provide it if pointed the right way.
I can pair, but it does not connect at all.
The text was updated successfully, but these errors were encountered: