Ive prepared the new implementation of the service. It has at least two advantages (compared to previous solutions) - it's adaptive (longer it takes to initialize devices - longer it waits between attempts, and these delays can be easily configured), and it does not reset already set devices. Because it doesn't use respawn feature, it doesn't litter logs with 'scary' messages.
** Attachment added: "rfkill-restore.conf" https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+attachment/3442157/+files/rfkill-restore.conf -- 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
