Comment 0 for bug 1376063
Revision history for this message
| Tony Espy (awe) wrote Bluetooth killswitch not always restored after reboot | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
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.