It\'s a bit wired here.
I have a problem is bluetoothctl always said \"No default controller available\". I found there are many people had same problem with me. But th
Also happens if rfkill switch is blocking Bluetooth (for some inadvertent reason, in my case):
$ rfkill list all
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: yes
Hard blocked: no
To unblock, pass the ID for your Bluetooth device from the list above to the unblock
subcommand:
$ rfkill unblock 0
Then controller should be back:
$ bluetoothctl list
Controller .... [default]