That seems overly complex, for what it's worth, I already have the design on how to fix this properly but haven't got around to implement it yet.
The changes will simply be to have the job trigger on bluetooth-device-added and network-device-added and store running state of the job so that we don't reset something we already set earlier at boot time. This should be a pretty minimal code change but will require a fair bit of testing to make sure we don't change the boot dependency tree in a way we don't want. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073669 Title: Bluetooth won't stay disabled after reboot due to early upstart job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
