Like you David, my BT headset is paired and connecting when switched on. The profile is also showing up in Sound Settings.
In my case though, the profile is not being autoselected in Sound Settings and manually selecting it does nothing. Sound is still routed through the wired amplified speakers.
pactl list | grep -i module-bluetooth-discover simply shows
Name: module-bluetooth-discover
Prior to switching on the headset: grep "pulseaudio.*bluetooth" /var/log/syslog shows nothing.
Post switching on the headset: grep "pulseaudio.*bluetooth" /var/log/syslog shows
pulseaudio[1928]: [pulseaudio] module.c: Module "module-bluetooth-discover" should be loaded once at most. Refusing to load.
pulseaudio[1928]: [pulseaudio] module-bluetooth-device.c: Failed to acquire transport /org/bluez/716/hci0/dev_00_0C_55_D1_91_ED/fd0
Like you David, my BT headset is paired and connecting when switched on. The profile is also showing up in Sound Settings.
In my case though, the profile is not being autoselected in Sound Settings and manually selecting it does nothing. Sound is still routed through the wired amplified speakers.
pactl list | grep -i module- bluetooth- discover simply shows bluetooth- discover
Name: module-
Prior to switching on the headset: grep "pulseaudio. *bluetooth" /var/log/syslog shows nothing.
Post switching on the headset: grep "pulseaudio. *bluetooth" /var/log/syslog shows bluetooth- discover" should be loaded once at most. Refusing to load. bluetooth- device. c: Failed to acquire transport /org/bluez/ 716/hci0/ dev_00_ 0C_55_D1_ 91_ED/fd0
pulseaudio[1928]: [pulseaudio] module.c: Module "module-
pulseaudio[1928]: [pulseaudio] module-