28

I recently installed ubuntu 20.04 and bluetooth seemed to work out-of-the-box. Yesterday, it stopped working with no known reason.

I can turn it ON but the settings still show it to be OFF.enter image description here

I tried the following:

$ sudo -i
$ rfkill list
0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
3: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

and on running bluetoothctl,

Agent registered
[bluetooth]# power off
No default controller available
[bluetooth]# power on
No default controller available
[bluetooth]# exit

What could be the problem and how to tackle it ?

2
  • 2
    Try sudo systemctl start bluetooth – Rayleigh Sep 6 '20 at 9:02
  • 2
    @Rayleigh It does nothing :/ – Pe Dro Sep 6 '20 at 11:34
9

I tried various hacks (all at once) and did a restart but I am not sure which led to the bluetooth working right.

I ran

sudo apt-get update
sudo apt upgrade
sudo systemctl start bluetooth
rfkill unblock bluetooth

And after the restart, it worked :?

4
  • 1
    Reading package lists... Done E: The repository 'ppa.launchpad.net/bluetooth/bluez/ubuntu focal Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. – ntg Oct 29 '20 at 21:35
  • 1
    Can confirm that the above commands work for me. Notice: I did not use the 1st command sudo add-apt-repository ppa:bluetooth/bluez, The reason is stated by @ntg – Franva Nov 5 '20 at 0:56
  • the issue comes again, this time, the above commands do not work again. – Franva Nov 12 '20 at 6:08
  • This does not help at all – Marecky Apr 9 at 23:39
8

I just experienced the exact same issue, always off in Gnome and no controller found. What do you see if you type the following in a terminal ?

dmesg | grep -i bluetooth

I had this log:

Bluetooth: hci0: Reading Intel version information failed (-110)

To resolve the problem, all I had to do was to perform a cold boot of my laptop.

Cf. comments in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592

2
  • 1
    Cold boot was the solution for me as well – user3079474 Nov 8 '20 at 11:04
  • 1
    Cold boot worked for me, too. By the way, just turning off and then booting did not work, but it worked when I completely (all LEDs off) disconnected the computer from the power by the switch and then turned it on. Is only the latter the cold boot? – Change-the-world Dec 1 '20 at 5:50
7

It's a bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592

Cold boot as in powering off from PC's source button (taking electricity off the mother board) worked for me. Just shutting down and having the motherboard LEDs on didn't work.

1
  • Thank you! Cannot believe this is the solution out of all those suggestions. – Grizzly Apr 9 at 10:49
2

This has happened to me before when I'd accidentally pressed the bluetooth on/off button on the laptop. (fn-F10 on my Thinkpad)

0

I had the same issue after installing a Windows 10 VM in a gnome-box and giving it access to bluetooth. After doing a clean shutdown of the WIN10 VM, bluetooth became available again on ubuntu.

1
  • 1
    I don't see how this relates to the question. Your issue was most likely caused by the VM taking over bluetooth, then releasing it when it wasn't needed. – ajgringo619 Dec 13 '20 at 6:29
0

I experienced a similar problem in my case I turned of the Bluetooth module from laptop mode tools, Restarted, and never had any problems regarding Bluetooth since then. Apparently, the LMT Bluetooth module is designed to save power by turning off Bluetooth and it really won't kill much of the battery by disabling it.

1
  • how did you do that? – Sayan Dey May 30 at 7:32
0

Worked for me:

sudo apt install linux-generic-hwe-18.04

Then restart the PC

Not the answer you're looking for? Browse other questions tagged or ask your own question.