[bluetoothctl]> power on
No default controller available
[bluetoothctl]>
Any ideas folks? Was all working before this. Have tried the applet and system settings and bluetooth cannot be enabled
also got this:
bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Mon 2026-05-18 19:15:30 BST; 27min ago
Invocation: 7cfaf96e74764c79abd71f5e4fc51288
Docs: man:bluetoothd(8)
Main PID: 2027 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 19021)
CPU: 32ms
CGroup: /system.slice/bluetooth.service
└─2027 /usr/libexec/bluetooth/bluetoothd
May 18 19:15:30 suse systemd[1]: Starting Bluetooth service...
May 18 19:15:30 suse (bluetoothd)[2027]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
May 18 19:15:30 suse bluetoothd[2027]: Bluetooth daemon 5.82
May 18 19:15:30 suse systemd[1]: Started Bluetooth service.
May 18 19:15:30 suse bluetoothd[2027]: Starting SDP server
May 18 19:15:30 suse bluetoothd[2027]: Bluetooth management interface 1.23 initialized
~
~
~
I have rolled back to 7.0.6-1 kernel till then new kernel with fix comes out. If you have btrfs snapshot you can easily select this kernel during boot menu.
run “sudo rfkill” <------ install if not installed
Look for bluetooth blocked. For me it is always blocked when bluetooth is not working. I am trying to fine out what blocks bluetooth but no info thusfar.
run “sudo rfkill unblock bluetooth”
rerun “sudo rfkill” to see that is is unblocked.
reboot – “sudo reboot”
Look at bluetooth icon in panel to see that it does not have a red (x).
Play some audio like youtube. Turn off your bluetooth, e.g., with the headphones on/off button. . Restart device, e.g., headphones with on/off button. On headphones you will hear “connected” two times.
No, this thread is about a specific issue with Mediatek cards.
BTW a fix should be in snapshot 20260520 that is just hitting the mirrors while I am writing.
Ya, I don’t think the back ported fix made it into the released kernel. At least from the kernels bug tracker it looks like the needed fix is in 7.0.10.