Looks like the problem is caused by "race condition" during startup - by the moment "rfkill-restore" gets executed the driver for bluetooth is not completelly initialized, so the script "does not see" the device, thus cannot switch it on/off. At least it was like this on my Ubuntu 12.04. I "solved" the problem (its rather a workaround than a solution) by adding line "sleep 1" in the beginning of the script (after line "script") in file /etc/init/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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
