I've confirmed this is still the case on a 2013-12018 update before touching /userdata/.writable_image, but bluetooth stays off after the image becomes writable.
This sounds a little like bug #1230275; however, indicator-bluetooth no longer pokes /dev/rfkill directly. Instead, it just powers the default bluez adapter on/off via bluez' dbus API. Is it possible that bluez is making changes that aren't getting saved due to permissions issues? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232828 Title: Bluetooth indicator comes back on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1232828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
