Bluetooth status in the Unity menu bar does not always match status in system settings

[w-sky]

When no Bluetooth device is connected and I turn off Bluetooth with the switch in the menu of the notification icon, the Bluetooth status in System Settings app is still "on" however Bluetooth seems to be off.

Also, when Bluetooth is turned on, the status of a paired device may show "connection on" in the notification icon menu when it is actually not connected, as System Settings do show correctly. In this case I have to switch off and on again if I want to activate the connection.

Also, I can not switch the connection to a paired device on or off with the System Settings app. The switches are grey and I can not click them, however they do always show the correct status.

Using: Ubuntu 19.10 with Unity desktop on Asus x571 laptop

Info:

unity: 7.5.0+19.10.20190924-0ubuntu1
unity-control-center: 15.04.0+19.10.20190921-0ubuntu1

service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-03-28 11:26:18 CET; 5h 42min ago
     Docs: man:bluetoothd(8)
 Main PID: 1035 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 3.5M
   CGroup: /system.slice/bluetooth.service
           └─1035 /usr/lib/bluetooth/bluetoothd

Mär 28 14:17:39 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd0: fd(22) ready
Mär 28 16:46:32 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12)
Mär 28 16:49:02 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd1: fd(22) ready
Mär 28 16:49:22 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12)
Mär 28 16:50:05 Abook bluetoothd[1035]: Control: Refusing unexpected connect
Mär 28 16:50:08 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd2: fd(22) ready
Mär 28 16:53:38 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12)
Mär 28 16:58:41 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12)
Mär 28 16:59:23 Abook bluetoothd[1035]: Control: Refusing unexpected connect
Mär 28 16:59:25 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd3: fd(22) ready

Bluetooth device:
T: Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#= 6 Spd=12 MxCh= 0
D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=8087 ProdID=0029 Rev=00.01
C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: unity-control-center 15.04.0+19.10.20190921-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Mar 28 16:53:08 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-01-20 (68 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

[Khurshid Alam (khurshid-alam)]

That's indicator-bluetooth. So not a u-c-c bug. Also the issue could be with gnome-bluetooth since it works fine on my machine.

Your error shows

"Failed to set mode: Blocked through rfkill (0x12) "...so the hardware is blocking it. Try running "sudo rfkill unblock all" but you may have to re-run it after each boot.