Those events come from the udev bridge, the two you're interested in are: - net-device-added - bluetooth-device-added
My idea was roughly to change /etc/init/rfkill-restore.conf with: - start on local-filesystems or (local-filesystems and net-device-added) or (local-filesystems and bluetooth-device-added) - Add a line after the echo, doing "touch /run/rfkill.$1.done" - Change the if statement not to trigger if /run/rfkill.$1.done exists This should make the job trigger once at boot time and again every time a device appears on the system, the entry in /run will be there to avoid restoring the original state of all devices every time a new device shows up. /run being on tmpfs, it won't be persistent across reboots. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
