Bug#806302: systemd does not start bluetooth.service if bluetooth soft rfkilled in the previous boot

Mattia Belluco dewanee at ninthfloor.org
Thu Nov 26 08:53:42 GMT 2015


Package: systemd
Version: 228-2
Arch:	amd64

If bluetooth is disabled by soft rfkill (blueman applet) the status
survives reboot and systemd no longer loads bluetoothd (which in turn
prevent blueman from loading) because:

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled;
vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Thu 2015-11-26 09:33:14 CET; 49s ago
           ConditionPathIsDirectory=/sys/class/bluetooth was not met
     Docs: man:bluetoothd(8)

from my understanding /sys/class/bluetooth appears only if rfkill is
disabled and in fact if I issue:

rfkill unblock tpacpi_bluetooth_sw

the relevant directory appears and I can manually start the deamon with

systemctl start bluetooth.service


regards

Mattia Belluco



More information about the Pkg-systemd-maintainers mailing list