Bluetooth Running, but cannot be Enabled

English Applications
1

Very recently, on KDE, I cannot enable bluetooth.

It does seems that the service is running…

sudo systemctl status bluetooth
[sudo] password for root: 
● bluetooth.service - Bluetooth service
     Loaded: loaded (/etc/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Sun 2026-05-17 20:51:01 PDT; 16min ago
 Invocation: b8901657246f4ccd9a9e40a54baeaeb2
       Docs: man:bluetoothd(8)
   Main PID: 2142 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 47179)
        CPU: 51ms
     CGroup: /system.slice/bluetooth.service
             └─2142 /usr/libexec/bluetooth/bluetoothd

May 17 20:51:00 localhost systemd[1]: Starting Bluetooth service...
May 17 20:51:00 localhost bluetoothd[2142]: Bluetooth daemon 5.82
May 17 20:51:00 localhost bluetoothd[2142]: Starting SDP server
May 17 20:51:00 localhost bluetoothd[2142]: Bluetooth management interface 1.23 initialized
May 17 20:51:01 localhost systemd[1]: Started Bluetooth service.

and it is not blocked either…

sudo rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked

I’ve looked around, and the only post I found that might have been in a similar situation is this post. However, I do not share their wifi/bluetooth card, I have a mediatek one.

02:00.0 Network controller: MEDIATEK Corp. MT7921 802.11ax PCIe Wireless Network Adapter [Filogic 330]

WIFI works fine for the most part, and bluetooth has previously worked for months, so what could be the issue?

2

Try bluetoothctl

Once you are in that shell, try scan on, for me that gives:

$ bluetoothctl 
Agent registered
[bluetoothctl]> scan on
SetDiscoveryFilter success
Discovery started
[CHG] Controller 02:1A:7D:FA:71:13 Discovering: yes
[NEW] Device 55:53:E4:8B:A7:85 55-5B-E4-8B-A0-45
[NEW] Device C2:18:53:8E:1A:4D C2-18-03-8E-1A-ED
[CHG] Device FD:6F:15:7A:2D:1C RSSI: 0xffffffbe (-66)
[CHG] Device FD:6F:15:7A:2D:1C ManufacturerData.Key: 0x0702 (1794)
[CHG] Device FD:6F:15:7A:2D:1C ManufacturerData.Value:
  21 04 04 00 00 09 0f                             !......
3

No, it seems bluetooth is broken in kernel 7.07, works with 7.06. bluetoothctl only says »Agent registered« and that’s it.

1 Like
4

There are many bug reports in bugzilla about bluetooth and see here:

Seems we have to wait for kernel 7.0.8.

5

I have the same. However can’t load 7.0.6 as nvidia driver was built for 7.0.7 and boot hangs completely. Loaded 6.18.31 longterm kernel now, however bluetooth is still unavailable.

1 Like
6

Could be but for me Bluetooth is working on 7.0.7:

$ uname -r
7.0.7-1-default

My USB adapter:

0a12:0001 e0 2IFs [USB 2.00, 12 Mbps, 100mA] (Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode))

7

Before writing you need to go and read original link:

It happens with MediaTek Bluetooth adapters, while you have Cambridge Silicon Radio, Ltd Bluetooth Dongle.

8

Still does not work with kernel 7.0.9

9

After bluetooth is runnung, try turning off your bluetooth device, e.g., headphones with the button on device. After 5 or 10 seconds, turn it back on. I get two connect messages in a row and then it starts working.

Give that a try.

tom kosvic

10

No, I can’t even enable it in KDE, no bluetooth devices listed at all!

See output:

bluetoothctl
Agent registered
[bluetoothctl]> scan on
No default controller available
11

There’s nothing you can do with it until the fix comes out.
I boot to the 6.19 kernel when I am using bluetooth.

12

I have only lontgerm 6.18, however bug was backported to it as well.

Yes, but there was a message it will be fixed in 7.0.8 or 7.0.9 and some people already reported issue was fixed for them, seems it was just for Fedora or Arch, now new message appear: in SUSE it will be fixed in 7.0.10.

13

There’s a couple of things going on here.

Fedora and Arch backported the fix from the 7.1 development tree and released a kernel with that fix.

That same fix was indeed backported to 7.0.9 in the stable kernel development tree which is why if you add that repository to your system and install 7.0.9 from there, it is fixed. What happened though is that that fix was applied to the Stable repository after the request to merge Stable to Factory to build an official openSuSE release, so it is not included in any snapshot.

It being fixed in 7.0.10 is coming from the official kernel release from kernel.org. The fix was officially backported from the 7.1 development tree and included in the 7.0 tree and will be there from 7.0.10 on without any special patches being maintained by the distros.

3 Likes
14

20260527 with kernel 7.0.10 got released literally just now which fixed bluethooth for me!

15

Can confirm Bluetooth also works for me after this update!

16

Thanks!
Confirmed also on my Kalpa system

17

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.