Keep Bluetooth disabled (rfkill-ed) after hibernate

Framework Laptop 13 Linux
1

Which Linux distro are you using?
Arch

Which kernel are you using?
6.11.3-zen1-1-zen

Which BIOS version are you using?
3.05

Which Framework Laptop 13 model are you using? AMD Ryzen™ 7040 Series

I have enabled rfkill-block@bluetooth.service to block Bluetooth automatically on boot. But I also have suspend-then-hibernate enabled, so I am frequently using hibernate. When I resume from hibernate, Bluetooth is enabled again. I saw Bluetooth disabled state not restored when resuming from disk · Issue #3026 · systemd/systemd · GitHub, which links a kernel bug report that seems to suggest it is a BIOS implementation issue, and that bluetooth should stay disabled even after resuming from disk if rfkilled.

Does anyone else have any experience with keeping Bluetooth disabled, especially while using hibernate? Is there a lower level fix for this instead of just making a script that does rfkill block bluetooth both on boot and on resume?

2

Also, is this the wrong category? It wouldn’t let me choose the “Framework Laptop 13 Linux” category because it kept saying I needed to choose two tags, but I couldn’t choose any second tag or anything after picking “arch” as the first one.