Allow users to escape broken rfkill state
@bberg
Submitted by Benjamin Berg Link to original bug (#782532)
Description
Due to bugs (which are being dealt with) users might end up in the following rfkill state which will persist unless the computer is re-installed.
$ rfkill list 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 121: hci0: Bluetooth Soft blocked: yes Hard blocked: no
This is bad, as GNOME considers bluetooth to be on but it is unable to actually turn it on (BluetoothAirplaneMode is Off). When the user tries to fix this by turning off/on bluetooth they will still be stuck in the same state as systemd-rfkill restores it when hci0 re-appears.
I see two possible workarounds right now:
- Detect the case that systemd-rfkill does a stupid restore and unblock again
- Allow the user to "Enable" bluetooth a second time in the control center (bug #764696 is related); main issue is that the switch would go back to "Off" for a short time when enabling.