Also, disabling bluetooth seems to be done entirely at the
rfkill/systemd/kernel level. BlueZ is not involved, and bluetoothd stays
active regardless. bluetoothd just loses access to the hardware when
it's disabled.
** Package changed: bluez (Ubuntu) => ubuntu
--
You received this bug notificati
It appears the state is stored by rfkill, in:
/var/lib/systemd/rfkill/*
Maybe Budgie isn't setting it (indirectly) properly...
John, can you please run this command and send us the output (after
disabling Bluetooth)?
grep . /var/lib/systemd/rfkill/*
Also, what is the name of the tool you a
I'm not sure what you mean by init scripts. Init scripts have long been
replaced by systemd.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1809783
Title:
Bluetooth always on when power
The bluetooth status should be store/restored by the bluez init scripts
** No longer affects: gnome-shell (Ubuntu)
** Package changed: gnome-bluetooth (Ubuntu) => bluez (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ub
Sounds related to bug 1518677.
** Package changed: bluez (Ubuntu) => gnome-bluetooth (Ubuntu)
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubun
5 matches
Mail list logo
