Hello,
I'm landing here after tracking a bug : I could not output sound to my SRS-XB22 bluetooth speaker.
I had in logs :
`src/service.c:btd_service_connect() a2dp-sink profile connect failed for F8:DF:15:7F:ED:AA: Protocol not available`
I did not understand why these commands were mandatory as I already have them in `/etc/pulse/default.pa`
Then I checked my `~/.config/pulse/default.pa` and found this :
```
#!/usr/bin/pulseaudio -nF
#
# Work around for PA not allowing access to A2DP profiles in the user session
# because GDM already has it open.
# LP: #1703415
# load system wide configuration
.include /etc/pulse/default.pa
### unload driver modules for Bluetooth hardware
.ifexists module-bluetooth-policy.so
unload-module module-bluetooth-policy
.endif
So here, we are : today, with
- Ubuntu 20.10
- Pulseaudio 1:13.99.2-1ubuntu2.1
- BlueZ 5.55-0ubuntu1.1
=> I do not reproduce the original bug.
=> Moreover, the now unnecessary workaround in `~/.config/pulse/default.pa` is preventing normal use for bluetooth devices.
**Workaround for the workaround** : comment the lines in `~/.config/pulse/default.pa`
```
#!/usr/bin/pulseaudio -nF
#
# Work around for PA not allowing access to A2DP profiles in the user session
# because GDM already has it open.
# LP: #1703415
# load system wide configuration
.include /etc/pulse/default.pa
### unload driver modules for Bluetooth hardware
#.ifexists module-bluetooth-policy.so
# unload-module module-bluetooth-policy
#.endif
#
Hello, c:btd_service_ connect( ) a2dp-sink profile connect failed for F8:DF:15:7F:ED:AA: Protocol not available`
I'm landing here after tracking a bug : I could not output sound to my SRS-XB22 bluetooth speaker.
I had in logs :
`src/service.
I found a workaround here https:/ /askubuntu. com/questions/ 1172000/ a2dp-sink- profile- connect- failed bluetooth- policy bluetooth- discover
```
$ pactl load-module module-
$ pactl load-module module-
```
I did not understand why these commands were mandatory as I already have them in `/etc/pulse/ default. pa`
Then I checked my `~/.config/ pulse/default. pa` and found this : bin/pulseaudio -nF
```
#!/usr/
#
# Work around for PA not allowing access to A2DP profiles in the user session
# because GDM already has it open.
# LP: #1703415
# load system wide configuration default. pa
.include /etc/pulse/
### unload driver modules for Bluetooth hardware bluetooth- policy. so bluetooth- policy
.ifexists module-
unload-module module-
.endif
.ifexists module- bluetooth- discover. so bluetooth- discover
unload-module module-
.endif
```
So here, we are : today, with 2-1ubuntu2. 1
- Ubuntu 20.10
- Pulseaudio 1:13.99.
- BlueZ 5.55-0ubuntu1.1
=> I do not reproduce the original bug.
=> Moreover, the now unnecessary workaround in `~/.config/ pulse/default. pa` is preventing normal use for bluetooth devices.
**Workaround for the workaround** : comment the lines in `~/.config/ pulse/default. pa` bin/pulseaudio -nF
```
#!/usr/
#
# Work around for PA not allowing access to A2DP profiles in the user session
# because GDM already has it open.
# LP: #1703415
# load system wide configuration default. pa
.include /etc/pulse/
### unload driver modules for Bluetooth hardware bluetooth- policy. so bluetooth- policy
#.ifexists module-
# unload-module module-
#.endif
#
#.ifexists module- bluetooth- discover. so bluetooth- discover
# unload-module module-
#.endif
```