Bug#778981:

[Felipe Sateler]

HI Adnan,

On 14 August 2015 at 06:43, Adnan Hodzic <adnan at hodzic.org> wrote:
>
> Hi Felipe,
>
> I have the same problem. My wireless headphones aren't detected by bluetooth.
>
> Apparently, running "pactl load-module module-bluetooth-discover" fixes the problem for a lot of people. But in my case this command just returns: "Failure: Module initialization failed".

This seems to happen because your device is correctly detected:

(   0.143|   0.000) D: [pulseaudio] bluez5-util.c: Device
/org/bluez/hci0/dev_6C_2F_F5_2B_19_66 found
(   0.143|   0.000) D: [pulseaudio] bluez5-util.c: Address: 6C:2F:F5:2B:19:66
(   0.143|   0.000) D: [pulseaudio] bluez5-util.c: Alias: 6C-2F-F5-2B-19-66
(   0.143|   0.000) D: [pulseaudio] bluez5-util.c: Adapter: /org/bluez/hci0
(   0.143|   0.000) D: [pulseaudio] bluez5-util.c: Unknown interface
org.freedesktop.DBus.Properties found, skipping
(   0.143|   0.000) D: [pulseaudio] backend-native.c: Bluetooth
Headset Backend API support using the native backend
(   0.143|   0.000) D: [pulseaudio] backend-native.c: Registering
Profile /Profile/HSPAGProfile
...
(   1.629|   0.000) E: [pulseaudio] module.c: Module
"module-bluetooth-discover" should be loaded once at most. Refusing to
load.
(   1.629|   0.000) I: [pulseaudio] client.c: Freed 1 "pactl"

You can't have bluetooth loaded twice.


But in your log it seems your wireless headset is not getting detected.
I fear your problem is on the bluetooth side, not pulse. Please try
checking if your device is really connected using bluetoothctl (use
the devices command to list known devices, and the info command to
show the status information for that device.


-- 

Saludos,
Felipe Sateler