This still seems to be a problem on Ubuntu 19.04. Ie, if I do: $ sudo systemctl status systemd-rfkill ● systemd-rfkill.service - Load/Save RF Kill Switch Status Loaded: loaded (/lib/systemd/system/systemd-rfkill.service; static; vendor preset: ...
$ rfkill block bluetooth $ rfkill ID TYPE DEVICE SOFT HARD 0 wlan phy0 unblocked unblocked 1 bluetooth hci0 blocked unblocked $ sudo reboot Then I get: $ rfkill ID TYPE DEVICE SOFT HARD 0 wlan phy0 unblocked unblocked 1 bluetooth hci0 unblocked unblocked and I can see that the state files in /var/lib/systemd/rfkill were not updated as part of the reboot: $ cat /var/lib/systemd/rfkill/*bluetooth 0 However, I can workaround this manually by running 'sudo /lib/systemd /systemd-rfkill' prior to reboot myself: $ rfkill block bluetooth $ rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth hci0 blocked unblocked 1 wlan phy0 unblocked unblocked $ sudo /lib/systemd/systemd-rfkill $ cat /var/lib/systemd/rfkill/*bluetooth 1 $ reboot $ rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth hci0 blocked unblocked 1 wlan phy0 unblocked unblocked $ cat /var/lib/systemd/rfkill/*bluetooth 1 In this manner, I can at least have bluetooth in a predictable state. However, the desirable behavior is likely to have the current state preserved across reboots. Looking at /lib/systemd/system/systemd- rfkill.service, it appears all that is missing is an ExecStop=/lib/systemd/systemd-rfkill.... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548057 Title: rfkill state is not restored on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1548057/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
