bluetoothd still running is correct and not a bug. Also, rfkill appears to show that the GUI/BlueZ has disabled the kernel device as much as it can:
0: hci0: Bluetooth Soft blocked: yes
So this is either a kernel bug or something missing from BlueZ's soft-blocking support.
bluetoothd still running is correct and not a bug. Also, rfkill appears to show that the GUI/BlueZ has disabled the kernel device as much as it can:
0: hci0: Bluetooth
Soft blocked: yes
So this is either a kernel bug or something missing from BlueZ's soft-blocking support.