This isn't up to the indicator. The indicator can toggle the
killswitches, but something else needs to persist the settings across a
reboot.
On phone, that's urfkill.
On computers, that's the rfkill-store/rfkill-restore jobs in the rfkill
package.
I'm setting the tasks for those, but things may change during the
development cycle to make it all managed by urfkill, which is the
"right" way to fix this for computers, and will still need a bit more
work on phone.
** Changed in: indicator-bluetooth
Status: New => Invalid
** Changed in: indicator-bluetooth (Ubuntu)
Status: Triaged => Invalid
** Also affects: urfkill (Ubuntu)
Importance: Undecided
Status: New
** Changed in: urfkill (Ubuntu)
Status: New => Triaged
** Changed in: urfkill (Ubuntu)
Importance: Undecided => High
** Also affects: rfkill (Ubuntu)
Importance: Undecided
Status: New
** Changed in: rfkill (Ubuntu)
Status: New => Triaged
** Changed in: rfkill (Ubuntu)
Importance: Undecided => Medium
** Changed in: urfkill (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: rfkill (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296114
Title:
Bluetooth is always enabled after reboot even if it was disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
