Created
April 11, 2016 12:42
-
-
Save freyes/dfc3f5232526a62bbc09adc816e0477d to your computer and use it in GitHub Desktop.
bluetoothd: a2dp-sink profile connect failed for AA:BB:CC:DD:EE:00: Protocol not available
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Source: https://g751jy.wordpress.com/about/parrot-zik-bluetooth-headset/ | |
https://bbs.archlinux.org/viewtopic.php?id=194006 | |
Cached: http://webcache.googleusercontent.com/search?q=cache:4stTobIXSD0J:https://g751jy.wordpress.com/about/parrot-zik-bluetooth-headset/+&cd=3&hl=en&ct=clnk&gl=us | |
Bug and possible solution: actually I found a bug in that make the headset unusable, it seems that the pulse audio module: module-bluetooth-discover works only if started after the X11 session is up. So I have a workaround. | |
Edit the file: | |
/etc/pulse/default.pa | |
and comment out (with an # at the beginning of the line) the following line: | |
#load-module module-bluetooth-discover | |
now edit the file: | |
/usr/bin/start-pulseaudio-x11 | |
and after the lines: | |
if [ x”$SESSION_MANAGER” != x ] ; then | |
/usr/bin/pactl load-module module-x11-xsmp “display=$DISPLAY session_manager=$SESSION_MANAGER” > /dev/null | |
fi | |
add the following line: | |
/usr/bin/pactl load-module module-bluetooth-discover | |
This way the Pulse audio’s Bluetooth modules will not be downloaded at boot time but after x11 is started. |
Thank you for sharing! After hours of trying different things this is what got my Bose QuietComfort 35 II to connect to my pop!OS 20.04 (based on Ubuntu 20.04).
@janhohner were you what else did you try? I am still not able to connect my Bose QC35.
Thank you so much! I was having trouble connecting my Sony Bluetooth headphones to my Ubuntu system (20.04.1 LTS). I was getting the same error you described. This fixed it, and probably saved me hours of trying different fixes.
THANK YOU SO MUCHHHHHHHHHHH, I CANT BELIVE IT I HAD THE PROBLEM FOR OVER 6 MONTHS THAMK YOU WE NEED MORE PEOPLE LIKE YOU
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
👍 glad to hear it still works :-)