You are not logged in.

#1 2021-03-28 20:25:34

MinePro120
Member
Registered: 2021-01-26
Posts: 4

bluetooth.service needs restart if bluetooth was blocked by rfkill

Hello! Consider the following scenario:
1) bluetooth.service is dead
2) hci0 is blocked by rfkill
3) bluetooth.service gets started
4) hci0 gets unblocked by rfkill

or, this one:
1) hci0 is unblocked
2) bluetooth.service is alive
3) hci0 gets blocked by rfkill
4) hci0 gets unblocked by rfkill

What happens is that bluetooth.service complains "Failed to set mode: Blocked through rfkill (0x12)" and needs a restart to function properly. Practically, that happens when blueman or blueberry block bluetooth using rfkill and turning it back on from the GUIs doesn't work on its own (as the service needs to be restarted). Is that normal? Any workarounds?

P.S. Based on this topic, a udev rule seems to be the answer, but what would that be, since hciconfig is deprecated? Also, the exact configuration seems to be working fine on Linux Mint without any rules (probably different bluez and blueberry versions though).

bluez-5.56-2, 5.11.10-arch1-1

Offline

#2 2021-04-07 03:48:19

bohemus
Member
Registered: 2021-04-07
Posts: 1

Re: bluetooth.service needs restart if bluetooth was blocked by rfkill

I m having precisely this same issue. Happens in Gnome, and Cinnamon as well. Did you ever find a fix for this?

Offline

Board footer

Powered by FluxBB