Bluetooth suddenly stopped working

I remember using Bluetooth before on this computer, but today when I tried to connect to my phone KDE just said “No Bluetooth adapters available”. The Bluetooth logo status light on my computer has turned off (I remember it being constantly on before).

$ lsusb | grep Blue 
Bus 003 Device 003: ID 0cf3:3004 Qualcomm Atheros Communications AR3012 **Blue**tooth 4.0

$ sudo rfkill list  
0: phy0: Wireless LAN 
       Soft blocked: no 
       Hard blocked: no 
1: hci0: Bluetooth 
       Soft blocked: no 
       Hard blocked: no

$ dmesg | grep -i blu 
   22.590030] **Blu**etooth: Core ver 2.22 
   22.590044] **Blu**etooth: HCI device and connection manager initialized 
   22.590048] **Blu**etooth: HCI socket layer initialized 
   22.590049] **Blu**etooth: L2CAP socket layer initialized 
   22.590055] **Blu**etooth: SCO socket layer initialized 
   24.884745] **Blu**etooth: hci0: don't support firmware rome 0x31010000 
   32.308813] **Blu**etooth: BNEP (Ethernet Emulation) ver 1.3 
   32.308814] **Blu**etooth: BNEP filters: protocol multicast 
   32.308817] **Blu**etooth: BNEP socket layer initialized

$ sudo hwinfo --bluetooth 
09: USB 00.0: 11500 Bluetooth Device                             
 [Created at usb.122] 
 Unique ID: eqBD.tx4ZIeIPK4B 
 Parent ID: uIhY.2DFUsyrieMD 
 SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0 
 SysFS BusID: 3-4:1.0 
 Hardware Class: bluetooth 
 Model: "Qualcomm Atheros AR3012 Bluetooth 4.0" 
 Hotplug: USB 
 Vendor: usb 0x0cf3 "Qualcomm Atheros Communications" 
 Device: usb 0x3004 "AR3012 Bluetooth 4.0" 
 Revision: "0.01" 
 Driver: "btusb" 
 Driver Modules: "btusb" 
 Speed: 12 Mbps 
 Module Alias: "usb:v0CF3p3004d0001dcE0dsc01dp01icE0isc01ip01in00" 
 Driver Info #0: 
   Driver Status: ath3k is active 
   Driver Activation Cmd: "modprobe ath3k" 
 Driver Info #1: 
   Driver Status: btusb is active 
   Driver Activation Cmd: "modprobe btusb" 
 Config Status: cfg=new, avail=yes, need=no, active=unknown 
 Attached to: #7 (Hub)

$ bt-device -l      
ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self)) 

Hope some of that command output helps.

Is this after a recent update? If so, how did you update?

A bit off-topic: did you try KDEconnect? Uses you wifi network

I always update using zypper dup. I don’t remember exactly when this stopped working, so I can’t say if it was right after an update. Since I am using TW, it could be the case.

I do use KDEConnect, but I was trying to do something, that KDEConnect can’t do.

Mmm, installed bluez-tools but everything’s OK here. Did you also try through the KDE bluetooth service and applet?

KDE settings say “No Bluetooth adapters available.”. The system tray icon says the same thing after clicking.

This seems to be the same issue


What’s the output of:

sudo systemctl status bluetooth


$ sudo systemctl status bluetooth● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running)
     Docs: man:bluetoothd(8)
 Main PID: 950 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─950 /usr/lib/bluetooth/bluetoothd

dub 08 11:31:46 OpenSUSE-WD-Elements-1042 systemd[1]: Starting Bluetooth service...
dub 08 11:31:46 OpenSUSE-WD-Elements-1042 bluetoothd[950]: Bluetooth daemon 5.49
dub 08 11:31:50 OpenSUSE-WD-Elements-1042 bluetoothd[950]: Starting SDP server
dub 08 11:31:50 OpenSUSE-WD-Elements-1042 bluetoothd[950]: Bluetooth management interface 1.14 initialized
dub 08 11:31:50 OpenSUSE-WD-Elements-1042 systemd[1]: Started Bluetooth service.

PS: Yes, I am aware of the fact, that WD Elements 1042 is a hard drive.

Poke. Has anyone found out anything interesting?

Does dmesg report anything re. bluetooth?

dmesg | grep -i blue

I am having exactly the same problem, with exactly the same output from commands, on Leap 42.3.

So, bluetooth has just started working out of nowhere. No idea how it happened.

If you are using the Atheros AR3012 it seems to be a duplicate chip ID error on two different card manufacturers and which firmware is loaded. At least it was on my hardware. I’m still running the old kernel listed in the bug report below to use bluetooth.