> systemctl status bluetooth.service > ● bluetooth.service - Bluetooth service > Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor > preset > Active: inactive (dead) > Condition: start condition failed at Sat 2018-03-03 18min ago > └─ ConditionPathIsDirectory=/sys/class/bluetooth was not met > Docs: man:bluetoothd(8) > lines 1-6/6 (END)
Interesting but not a blueman issue. Your kernel seems to not provide /sys/class/bluetooth when the soft block is enabled and the bluetooth.service file specifies to not start bluetoothd in that case. Personally I cannot reproduce that behavior. If I soft-block bluetooth and reboot, I *do* get an (empty) /sys/class/bluetooth so bluetoothd *does* get started. If you consider this a bug, it's either your linux-image not creating /sys/class/bluetooth or bluez having the unnecessary(?) ConditionPathIsDirectory=/sys/class/bluetooth. There is a similar report in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806302.
