I thought I had posted this problem yesterday, but am unable to find it now. So perhaps I didn't. However, if I am reposting, my apologies.

I run Linux Mint 16 'Petra' on an Asus Eeepc. The kernel is 3.11.0-12-generic. I have just acquired a Bose Soundlink III Bluetooth speaker, and was trying to stream music from my netbook to the speaker. I have managed to set up some sort of connection between the two - the Soundlink shows up on the Blueman screen. HOwever, when I try and set up the AudioSink for streaming music, I get the message: "Failed to connect. Stream setup failed." It seems to connect - a steady white light shows for a fraction on the speaker, but then reverts to the blue blink which indicates that it is back to the searching mode.

By the way, I am able to connect my phone to the speaker, so apparently the bluetooth stuff on the speaker is all right.

I realize that I am not the first person to have had this kind of problem. But a search through similar threads did not turn up anything that worked for me. Be greateful for any help. Thanks.

Have you been able to successfully connect any other device via bluetooth to the netbook? I'm not too familiar with Mint, but if its systemd, What is the output of or if not systemd

I don't know what is systemd

However, grep bluetooth and dmesg | grep bluetooth both produce no output at all.

Strange. What about ?

systemctl: command not found

OK. So it appears Petra does not use Systemd. Try

In response to service bluetooth status

bluetooth start/running, process 666

All right that's a good start, what about

1: asus-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no

2: asus-bluetooth
Soft blocked: no
Hard blocked: no

3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

4: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

Hi Alok_Rai,

In my experience with Bluetooth on linux and sound devices (headphones, speakers ...), certain pulseaudio components were also required (minimally, pulseaudio-bluetooth, if memory serves ...).

I am not a regular Mint user, so I can't get into specifics concerning its support for bluetooth audio. However, I would suggest reading anything the distro provides in the way of documentation.

I use bluetooth audio regularly on Arch, but I don't use GUI tools. After making sure the proper software components are installed, I simply start pulseaudio, start the bluetooth service and then connect to the speaker with bluetoothctl. Mint probably has a GUI tool to manage all or part of this.

Still, your problem sounds suspiciously like the experience I had before finding out that the pulseaudio-bluetooth package was a pre-requisite.

Hope this helps.

Cheers !

Ok, so I'm no expert but it looks like the service starts fine and there are no soft or hard blocks preventing connectivity but it also looks like your computer might have 2 bluetooth adapters.

Let's see if we can find the adapter(s). What is the output of and

Good morning!

Here is the output from my attempt to install pulseaudio-bluetooth:

sudo apt-get install pulseaudio-bluetooth
[sudo] password for alok:
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_saucy_main_i18n_Translation-en
E: The package lists or status file could not be parsed or opened.


Here is the output from running lspci from Terminal:

$ lspci
00:00.0 Host bridge: Intel Corporation Atom Processor D2xxx/N2xxx DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02)
00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 4 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation NM10/ICH7 Family SATA Controller [IDE mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
03:00.0 Ethernet controller: Qualcomm Atheros AR8152 v2.0 Fast Ethernet (rev c1)


And here is the output from running lsusb from Terminal:

$ lsusb
Bus 001 Device 003: ID 13d3:5711 IMC Networks
Bus 001 Device 002: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 13d3:3315 IMC Networks Bluetooth module
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


Thank you for being patient!

If you haven't already, go ahead and follow these instructions for installing the Broadcom 4313 driver and test your bluetooth again

I followed the link given but realized quickly that I was way outside my depth!

Still, I find that the penultimate line in the lspci output indicates that the BCM4313 Wireless Adapter is there, so perhaps the problem lies somewhere else?

Yes, the adapter is there, but it may not have loaded the driver properly. For instance, on my Asus G751JM, I have a similar wireles/bluetooth combo card, and while the wireless worked I had to fix the bluetooth side of it still. Go ahead and run that should let us know if the driver is installed or not.