[Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job
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
[Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job
@Kyle Ya, I agree, there are better solutions, 1 sec delay solution was just a compromise -- 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
[Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job
Ive just noticed the patch. Tried it - works for me. Maybe it still makes sense to add constant 1 sec delay in beginning of the script (and maybe reduce conditional delays to 3 sec to balance timings). I think its important, because for all users, who encounter this problem, the service is going to be respawned at least once with 5 sec delay. Introducing 1 sec constant delay makes the script work for most cases from the first try. Also, the first if-block detects if rfkill stuff is available at all, so there is no point in restarting the service in this case. Kyle's file from the first comment with above changes is attached to this comment. ** Attachment added: "rfkill-restore.conf" https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+attachment/3440869/+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
[Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job
Ive had the same problem on Ubuntu 12.04 - bluetooth applet used to "forget" the state during shutdown, and switched bluetooth on during startup. I was able to solve it by removing my "internet-over-bluetooth" profile from NetworkManager. As I saw from the logs, even though I didnt use this "profile", NetworkManager anyway took the control over bluetooth device and switched it on during startup. So, maybe in your case there is also some third-party service that switches bluetooth on? -- 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
