Am 26.11.2015 um 09:53 schrieb Mattia Belluco: > 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
I'm confused, why is this a bug in particular (you disabled bluetooth) and systemd specifically (bluetooth.service is not shipped by systemd)? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
