Bluetooth won't stay disabled after reboot due to early upstart job
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rfkill (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Using a Dell XPS 13 with Ubuntu 12.04.
In order to restore RF interfaces to their previous state between boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-store.conf (run while shutting down) and rfkill-restore.conf (run when starting up). However, while rfkill-restore.conf starts on the Upstart local-filesystems signal, there is a high probability that the RF kill switches in /sys/class/rfkill/ still won't yet be populated (i.e. every time on the Dell XPS 13). This results in behavior like the following:
1. Disable bluetooth via applet.
2. Reboot.
3. Login.
4. Observe bluetooth is re-enabled!
Bluetooth should have stayed disabled, but since the kill switches weren't present when rfkill-restore was run, the kill switch states were not restored.
Changed in rfkill (Ubuntu): | |
assignee: | nobody → Kyle Fazzari (kyle.f) |
assignee: | Kyle Fazzari (kyle.f) → nobody |
Changed in rfkill (Ubuntu): | |
assignee: | Stéphane Graber (stgraber) → nobody |
tags: | added: xenial |
I have attached a new rfkill-restore script that respawns for up to 60 seconds if the kill switches aren't present. If, after a minute, the switches still aren't present, the upstart job fails.