Comment 7 for bug 1318875
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Seems to me like this is an issue at two levels:
1) Settings should be speaking to NM and bluez (or another piece) to disable wifi, bluetooth, and those should save their states
2) There is currently nothing to save the states for all radios in a reliable manner. NM saves its own states, bluetooth doesn't save anything (that's expected to be handled by the rfkill subsystem, but that doesn't save soft states)
So, it seems to me like the best course of action at this moment is to outright *remove* the airplane mode switch, because it's confusing to users in not quite doing what it should be and saving its state.
Another option would be to save the airplane mode switch state in gconf/gsettings, but there is nothing on the desktop that would start on boot and read that value to apply necessary changes like bringing down bluetooth again.