| 2014-09-30 23:59:46 |
Tony Espy |
description |
Devices: mako, krillin
Images: RTM #63/#72
When Bluetooth is disabled from the indicator or system settings, it's state is not being persisted to urfkill's saved-states file, so if the system is restarted, BT will be enabled.
If however, BT is disabled, then FlightMode enabled, the state file is correctly updated and if/when FM is disabled ( even after a reboot ), BT will stay disabled, and if rebooted again will still be disabled. This is because when FM is enabled, the state file is updated whereas when the BT rfkill device changes, even though urfkill registers it, it doesn't update the state file.
Note - this is similar to bug #1296114 which was reported against a 14.04 x86 desktop. |
Devices: mako, krillin
Images: RTM #63/#72
Extra Packages: urfkill - 0.6.0~20140923.183149.c5012c3.1-0ubuntu1
Note - the above version of urfkill is currently being silo-tested.
When Bluetooth is disabled from the indicator or system settings, it's state is not being persisted to urfkill's saved-states file, so if the system is restarted, BT will be enabled.
If however, BT is disabled, then FlightMode enabled, the state file is correctly updated and if/when FM is disabled ( even after a reboot ), BT will stay disabled, and if rebooted again will still be disabled. This is because when FM is enabled, the state file is updated whereas when the BT rfkill device changes, even though urfkill registers it, it doesn't update the state file.
Note - this is similar to bug #1296114 which was reported against a 14.04 x86 desktop. |
|
