DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi" has no effect #845
Description
Hi,
Would it be possible for TLP to only mask systemd-rfkill.socket/service when either
RESTORE_DEVICE_STATE_ON_STARTUP & DEVICES_TO_DISABLE_ON_STARTUP are set?
And to not mask/modify it when none are set and TLP_DISABLE_DEFAULTS=1?
I've been trying to use RESTORE_DEVICE_STATE_ON_STARTUP &
DEVICES_TO_DISABLE_ON_STARTUP without success.
If I have RESTORE_DEVICE_STATE_ON_STARTUP=1 and I do bluetooth off and wifi off
before a reboot, bluetooth and wi-fi are still activated after.
If I have RESTORE_DEVICE_STATE_ON_STARTUP=0 and
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi", both are still
activated after a reboot as well.
Now don't get me wrong, I'm not blaming TLP at all. I know there is a lot of
variables outside of TLP configuration that walk over each other. For example, I
couldn't disable bluetooth at boot by modifying grub nor by editing
/etc/bluetooth/main.conf, only disabling it through systemd worked.
Maybe some race condition involved outside TLP, that's why I didn't report this
as a bug.
Now I know I can unmask rfkill manually, but since I'm not using these TLP features,
I don't think TLP should disable it automatically, because some other program
might depend on rfkill.
What do you think?