Ok, I first did a quick test here and my BT headset paired, showed up in sound settings, worked as usual, and profile was selectable. So at least the problem is not *that* generic.
Anyway, module-bluetooth-discover is loaded from /etc/pulse/default.pa, which is run every time pulseaudio starts. If it did not load, hopefully there is some related error in syslog.
So if you can verify that module-bluetooth-discover is indeed *not* loaded (i e does not show up in "pactl list modules"), hopefully there should be an error message in syslog indicating why it did not start. So, could you do a:
grep "pulseaudio.*bluetooth" /var/log/syslog
...to see if you find anything that looks suspicious?
Ok, I first did a quick test here and my BT headset paired, showed up in sound settings, worked as usual, and profile was selectable. So at least the problem is not *that* generic.
Anyway, module- bluetooth- discover is loaded from /etc/pulse/ default. pa, which is run every time pulseaudio starts. If it did not load, hopefully there is some related error in syslog.
So if you can verify that module- bluetooth- discover is indeed *not* loaded (i e does not show up in "pactl list modules"), hopefully there should be an error message in syslog indicating why it did not start. So, could you do a: *bluetooth" /var/log/syslog
grep "pulseaudio.
...to see if you find anything that looks suspicious?
Thanks!