Ubuntu – Bluetooth can’t find headphones

18.10a2dpbluetoothcommand linesound

When I activate bluetooth on my notebook I can see and pair with every bluetooth device near me but there is no A2DP or HFP/HSP headphones in there. Typing
service bluetooth status
in terminal gives me back

    bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-11-07 12:35:12 MSK; 1h 2min ago
     Docs: man:bluetoothd(8)
 Main PID: 1189 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4331)
   Memory: 2.5M
   CGroup: /system.slice/bluetooth.service
           └─1189 /usr/lib/bluetooth/bluetoothd

ноя 07 12:35:10 r3t4rd-K56CB systemd[1]: Starting Bluetooth service...
ноя 07 12:35:11 r3t4rd-K56CB bluetoothd[1189]: Bluetooth daemon 5.50
ноя 07 12:35:12 r3t4rd-K56CB systemd[1]: Started Bluetooth service.
ноя 07 12:35:12 r3t4rd-K56CB bluetoothd[1189]: Starting SDP server
ноя 07 12:35:13 r3t4rd-K56CB bluetoothd[1189]: Bluetooth management interface 1.14 initialized
ноя 07 12:35:28 r3t4rd-K56CB bluetoothd[1189]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource
ноя 07 12:35:28 r3t4rd-K56CB bluetoothd[1189]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink
ноя 07 13:31:50 r3t4rd-K56CB bluetoothd[1189]: Unable to get io data for :1.50/Profile/HSPHSProfile/00001108-0000-1000-8000-00805f9b34fb:

Full restart of bluetooth service and typing service bluetooth status again just removed last line from the feedback.
I'm new to Linux systems so I can't get what to do next, can you lead me?

Best Answer

killing org.bluez process through sudo kill <org.bluez PID>,

then I wrote

rfkill block bluetooth
sudo service bluetooth stop
sudo rfkill unblock bluetooth

Bluetooth have been swithed off and then on after typing these commands, and my headphones appeared in devices list. Thanks to that answer

Related Solutions

Ubuntu – Lost bluetooth functionality after upgrading from 17.04 to 17.10

I've upgraded Kubuntu from 17.04 to 17.10 yesterday.

Mostly the same issue for me, I'm no longer able to connect my bluetooth speaker (RYGHT TANK) even though my bluetooth service is running.

Here is my sudo service bluetooth status and dmesg | grep -i blue results:

soul@soul-ZBOX-ID88-ID89-ID90:~$ sudo service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2017-10-27 23:50:19 CEST; 5min ago
     Docs: man:bluetoothd(8)
 Main PID: 11613 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─11613 /usr/lib/bluetooth/bluetoothd

oct. 27 23:50:18 soul-ZBOX-ID88-ID89-ID90 systemd[1]: Starting Bluetooth service...
oct. 27 23:50:19 soul-ZBOX-ID88-ID89-ID90 bluetoothd[11613]: Bluetooth daemon 5.46
oct. 27 23:50:19 soul-ZBOX-ID88-ID89-ID90 systemd[1]: Started Bluetooth service.
oct. 27 23:50:19 soul-ZBOX-ID88-ID89-ID90 bluetoothd[11613]: Starting SDP server
oct. 27 23:50:19 soul-ZBOX-ID88-ID89-ID90 bluetoothd[11613]: Bluetooth management interface 1.14 initialized

soul@soul-ZBOX-ID88-ID89-ID90:~$ dmesg | grep -i blue
[   21.008903] Bluetooth: Core ver 2.22
[   21.008918] Bluetooth: HCI device and connection manager initialized
[   21.008920] Bluetooth: HCI socket layer initialized
[   21.008922] Bluetooth: L2CAP socket layer initialized
[   21.008927] Bluetooth: SCO socket layer initialized
[   31.455093] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   31.455095] Bluetooth: BNEP filters: protocol multicast
[   31.455098] Bluetooth: BNEP socket layer initialized
[  116.012720] Bluetooth: RFCOMM TTY layer initialized
[  116.012730] Bluetooth: RFCOMM socket layer initialized
[  116.012738] Bluetooth: RFCOMM ver 1.11

A print screen of the message after trying to connect: connecting failure

Any idea?

EDIT (11/05):

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2017-11-05 09:42:42 CET; 7h ago
     Docs: man:bluetoothd(8)
 Main PID: 958 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─958 /usr/lib/bluetooth/bluetoothd

nov. 05 09:42:40 soul-ZBOX-ID88-ID89-ID90 systemd[1]: Starting Bluetooth service...
nov. 05 09:42:40 soul-ZBOX-ID88-ID89-ID90 bluetoothd[958]: Bluetooth daemon 5.46
nov. 05 09:42:42 soul-ZBOX-ID88-ID89-ID90 bluetoothd[958]: Starting SDP server
nov. 05 09:42:42 soul-ZBOX-ID88-ID89-ID90 bluetoothd[958]: Bluetooth management interface 1.14 initialized
nov. 05 09:42:42 soul-ZBOX-ID88-ID89-ID90 systemd[1]: Started Bluetooth service.
nov. 05 16:32:46 soul-ZBOX-ID88-ID89-ID90 bluetoothd[958]: a2dp-sink profile connect failed for FC:58:FA:55:F4:68: Protocol not available
nov. 05 16:32:54 soul-ZBOX-ID88-ID89-ID90 bluetoothd[958]: a2dp-sink profile connect failed for FC:58:FA:55:F4:68: Protocol not available
nov. 05 16:33:02 soul-ZBOX-ID88-ID89-ID90 bluetoothd[958]: a2dp-sink profile connect failed for FC:58:FA:55:F4:68: Protocol not available

EDIT (11/05) (after having installed pulseaudio-module-bluetooth):

soul@soul-ZBOX-ID88-ID89-ID90:~$ service bluetooth status
    ● bluetooth.service - Bluetooth service
       Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
       Active: active (running) since Sun 2017-11-05 17:05:04 CET; 3min 32s ago
         Docs: man:bluetoothd(8)
     Main PID: 875 (bluetoothd)
       Status: "Running"
        Tasks: 1 (limit: 4915)
       CGroup: /system.slice/bluetooth.service
               └─875 /usr/lib/bluetooth/bluetoothd

    nov. 05 17:04:57 soul-ZBOX-ID88-ID89-ID90 systemd[1]: Starting Bluetooth service...
    nov. 05 17:04:58 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: Bluetooth daemon 5.46
    nov. 05 17:05:04 soul-ZBOX-ID88-ID89-ID90 systemd[1]: Started Bluetooth service.
    nov. 05 17:05:04 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: Starting SDP server
    nov. 05 17:05:05 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: Bluetooth management interface 1.14 initialized
    nov. 05 17:06:23 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource
    nov. 05 17:06:23 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSink
    nov. 05 17:07:23 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
    nov. 05 17:07:23 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: connect error: Connection refused (111)
    nov. 05 17:07:26 soul-ZBOX-ID88-ID89-ID90 bluetoothd[875]: connect error: Connection refused (111)

EDIT (11/05 got it!): I ended up with a solution:

sudo apt install kmix
reboot

then

sudo apt install pulseaudio-module-bluetooth
reboot
pactl load-module module-bluetooth-discover

(last command may fail)

Then remove all your saved bluetooth devices and pair them again.

Do not forget to set the bluetooth devices at the top of the list of audio configuration:

Ubuntu – Ubuntu 18.04, Bluetooth is DEAD

Not sure for your case:

Verify the network driver.

Try the following commands:

rfkill block bluetooth
rfkill unblock bluetooth

Best Answer

Related Solutions

Ubuntu – Lost bluetooth functionality after upgrading from 17.04 to 17.10

Ubuntu – Ubuntu 18.04, Bluetooth is DEAD

Related Question