Bluetooth can not be enabled in KDE settings

Hello,

Two days ago I had a lot of updates, including ones for Bluetooth and wifi. I installed just before shutting down the computer, late in the evening.
Yesterday I could use my bluetooth headphones without problems until a restart.
From that moment on it is impossible to enable Bluetooth in the KDE settings.
I thought it was caused by the updates the day before but then realized it would be strange since I had used the headphones the whole morning, which was after the updates.
I then restored a Timeshift backup from Saturday morning, but still no Bluetooth.

The Bluetooth service ia active and running:

systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Mon 2022-01-31 06:17:50 CET; 9h ago
       Docs: man:bluetoothd(8)
   Main PID: 2942 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4915)
        CPU: 18ms
     CGroup: /system.slice/bluetooth.service
             └─2942 /usr/libexec/bluetooth/bluetoothd

Jan 31 06:17:50 localhost systemd[1]: Starting Bluetooth service...
Jan 31 06:17:50 localhost bluetoothd[2942]: Bluetooth daemon 5.62
Jan 31 06:17:50 localhost systemd[1]: Started Bluetooth service.
Jan 31 06:17:50 localhost bluetoothd[2942]: Starting SDP server
Jan 31 06:17:50 localhost bluetoothd[2942]: Bluetooth management interface 1.21 initialized

lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
Bus 001 Device 011: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 25a7:6672 Areson Technology Corp OKLIC
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
dmesg | grep Blue
    5.269942] Bluetooth: Core ver 2.22
    5.269974] Bluetooth: HCI device and connection manager initialized
    5.269978] Bluetooth: HCI socket layer initialized
    5.269980] Bluetooth: L2CAP socket layer initialized
    5.269982] Bluetooth: SCO socket layer initialized
    5.479754] Bluetooth: hci0: unexpected event for opcode 0x0000
    5.503042] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    5.503045] Bluetooth: BNEP filters: protocol multicast
    5.503050] Bluetooth: BNEP socket layer initialized
    9.497717] Bluetooth: hci0: Controller not accepting commands anymore: ncmd = 0
   15.641781] Bluetooth: hci0: sending initial HCI reset failed (-110)

In the dmesg command I see some things which are not correct, I guess.

Bluetooth: hci0: unexpected event for opcode 0x0000
Bluetooth: hci0: Controller not accepting commands anymore: ncmd = 0
Bluetooth: hci0: sending initial HCI reset failed (-110)

What else can I check to find the problem or do to fix this problem?

Thanks

  • “rfkill list” – please check the Bluetooth status – you may have to (rfkill
    ) unblock the Bluetooth device …

Thanks dcurtisfra for your fast reply.

This is what I get with the command you sent me:

sudo rfkill list
[sudo] password for root: 
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

@JanMussche:

If you haven’t already done so, please install the package “bluez-tools”.

  • Then execute “bt-adapter --list” to discover which adapters are present on your systems and then, execute “bt-adapter --info” to list the properties of the default adapter.
    You’ll have to add “–adapter «name|mac»” if you have more than one adapter on your system.

There is certainly something wrong here:

bt-adapter --list
No adapters found

Is your bluetooth build in or is it a USB stick?

If it is a USB stick, remove it, start on the console “dmesg --follow-new” and insert the USB stick. Then post the output of dmesg here.

No, it is build-in. Is there something I can do with that type?

I should have read your initial post better:

Bus 003 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface

I guess what is missing is a driver for this device, but I see it should be supported by the kernel, see https://linux-hardware.org/index.php?id=usb:8087-0a2a
Can you check what “sudo modprobe -v btusb” is giving?

Bug report may help.

It’s not much but this is all I got:

sudo modprobe -v btusb
[sudo] password for root:

And the plot thickens. :slight_smile:

Another thing to try:

sudo hwinfo --bluetooth

Thank you for still helping me. This is what I got from the command you suggested:

sudo hwinfo --bluetooth
[sudo] password for root: 
01: USB 00.0: 11500 Bluetooth Device                            
  [Created at usb.122]
  Unique ID: ds7n.l148Ao7nQK1
  Parent ID: mZxt.d7FDLX76qXB
  SysFS ID: /devices/pci0000:00/0000:00:08.1/0000:02:00.4/usb3/3-2/3-2.2/3-2.2:1.0
  SysFS BusID: 3-2.2:1.0
  Hardware Class: bluetooth
  Model: "Intel Bluetooth wireless interface"
  Hotplug: USB
  Vendor: usb 0x8087 "Intel Corp."
  Device: usb 0x0a2a "Bluetooth wireless interface"
  Revision: "0.01"
  Driver: "btusb"
  Driver Modules: "btusb"
  Speed: 12 Mbps
  Module Alias: "usb:v8087p0A2Ad0001dcE0dsc01dp01icE0isc01ip01in00"
  Driver Info #0:
    Driver Status: btusb is active
    Driver Activation Cmd: "modprobe btusb"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #12 (Hub)

I reported a bug report but the status is still new. It’s here: 1195461 – Bluetooth can't be enabled

In the bugreport at: https://bugzilla.opensuse.org/show_bug.cgi?id=1195461 I received a tip from Takashi Iwai:
Please give the full dmesg output after a fresh boot, and the output of hwinfo.

Also, you can try to turn off your machine and power off completely once (unplug the power cable), then retry. The BT error -110 is often related with an intel chip initialization problem.

My respond to him:
You are a genius. I let the laptop battery run dry until 3% at which it was shutdown automatically.
After plugging in the power cord and a cold start Bluetooth is working again. Amazing.
Thank you very much for your help. I marked this bug as resolved and Fixed.

Hi!

I have a similar problem, only I have a Bluetooth USB adapter. After executing the “dmesg --follow-new” command and inserting the device, Konsole displays the following message:

132.935070] usb 1-7: new full-speed USB device number 5 using xhci_hcd
133.084669] usb 1-7: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91
133.084682] usb 1-7: New USB device strings: Mfr=0, Product=2, SerialNumber=0
133.084687] usb 1-7: Product: BT DONGLE10
133.088362] Bluetooth**: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once…**

What should I do next, please tell me?