No default controller available in bluetooth

The bluetooth service isn’t running. I gave you the command to enable it. Then check the status again.

I get this:

[usr@DESKTOP-USR ~]$ sudo systemctl enable bluetooth.service && sudo systemctl start --now bluetooth.service
[usr@DESKTOP-USR ~]$ sudo bluetoothctl
Waiting to connect to bluetoothd...

Did you check the status again after enabling it to make sure it’s running.

sudo systemctl status bluetooth

Yes, same result unfortunately.

○ bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

Jul 07 17:51:06 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (Conditio>
Jul 07 17:51:36 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (Conditio>
Jul 07 17:52:31 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (Conditio>
Jul 07 18:02:01 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (Conditio>
Jul 07 18:05:42 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (Conditio>
Jul 07 18:07:21 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (Conditio>

OMG

Please show the output of this command!

sudo systemctl status bluetooth
○ bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

Jul 07 17:51:06 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (Conditio>
Jul 07 17:51:36 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (Conditio>
Jul 07 17:52:31 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (Conditio>
Jul 07 18:02:01 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (Conditio>
Jul 07 18:05:42 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (Conditio>
Jul 07 18:07:21 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (Conditio>

Your Ideapad has an Fn-key for turning airplane mode on / off!

Fn + :airplane: (airplane-symbol looking little different, ‘flying in left direction’)

:laughing:

1 Like

Yes i asked that too. Airplane mode turns WiFi and Bluetooth off.

You can try the command this way but check this first. What does rfkill show?

rfkill

sudo systemctl enable --now bluetooth

Then check status

sudo systemctl status bluetooth

When I press this, the WiFi gets turned on and off. It doesn’t seem to have effect on the Bluetooth…

It has to be on as the bluetooth is part of the WiFi chip.

Edit: Nothing is going to work if the bluetooth isn’t turned on and the blutooth service isn’t enabled and started.

1 Like
$ rfkill
ID TYPE      DEVICE                 SOFT      HARD
 0 wlan      ideapad_wlan      unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 wlan      phy0              unblocked unblocked

[usr@DESKTOP-USR ~]$ sudo systemctl enable --now bluetooth

[sudo] password for usr: 
[usr@DESKTOP-USR ~]$ sudo systemctl status bluetooth
○ bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

Jul 07 17:51:06 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condit>
Jul 07 17:51:36 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condit>
Jul 07 17:52:31 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condit>
Jul 07 18:02:01 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condit>
Jul 07 18:05:42 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condit>
Jul 07 18:07:21 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condit>
Jul 07 18:20:03 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condit>
lines 1-12/12 (END)...skipping...
○ bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

Jul 07 17:51:06 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Jul 07 17:51:36 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Jul 07 17:52:31 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Jul 07 18:02:01 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Jul 07 18:05:42 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Jul 07 18:07:21 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Jul 07 18:20:03 DESKTOP-USR systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).

You are sure WiFi is turned on?

Pretty sure, I’m messaging you now on the WiFi :slight_smile: .
image

uname -r gives the active kernel.

Can you post the output here?

Did you happen to remove something?

sudo pacman -S --needed bluez bluez-utils

Sure!

5.18.9-arch1-1

try this:

sudo pacman -S linux-lts-headers linux-lts

then:

sudo reboot

It doesn’t seem like that:

warning: bluez-5.64-2 is up to date -- skipping
warning: bluez-utils-5.64-2 is up to date -- skipping
 there is nothing to do

Try as @anon11595408 suggests to see if it will work on the lts kernel.