Thanks for your patience.
Sounds like confirmation that tlp is the "problem". (Un)fortunately tlp
is not a standard part of Ubuntu (yet). From what I remember, the
reasons are because it does cause bugs like this one.
** Package changed: ubuntu => tlp (Ubuntu)
** Summary changed:
- Bluetooth
sudo systemctl status systemd-rfkill :
● systemd-rfkill.service - Load/Save RF Kill Switch Status
Loaded: loaded (/lib/systemd/system/systemd-rfkill.service; static; vendor
preset: enabled)
Active: inactive (dead) since Sun 2019-01-13 08:55:19 CET; 1min 20s ago
Docs:
At least briefly for testing, yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809783
Title:
Bluetooth always on when power on my laptop (Budgie Desktop)
To manage notifications about this bug
I've read on some websites like ArchLinux Wiki and TecMint that the tlp
package is not crucial but it's important for power management. I'm
using Budgie on a laptop so battery life is meaningful for me. So do you
advise me to remove tlp anyway?
--
You received this bug notification because you
Thanks John. That confirms you do indeed have TLP installed. So now the
steps to answer comment #15 are something like:
sudo apt purge tlp tlp-rdw
and then after it's been uninstalled, reboot and run:
sudo systemctl status systemd-rfkill
--
You received this bug notification because you
Here it is
** Attachment added: "allpackages.txt"
https://bugs.launchpad.net/ubuntu/+bug/1809783/+attachment/5228379/+files/allpackages.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809783
John, please run:
dpkg -l > allpackages.txt
and then send us the resulting file 'allpackages.txt'.
** Changed in: budgie-desktop (Ubuntu)
Status: New => Incomplete
** Package changed: budgie-desktop (Ubuntu) => ubuntu
--
You received this bug notification because you are a member
"If you purge the tlp package and check the status/start the systemd-rfkill
service and reboot what happens?"
I don't understand what you mean. I'm not an experienced user, I'm sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
sudo systemctl start systemd-rfkill:
Failed to start systemd-rfkill.service: Unit systemd-rfkill.service is
masked.
No folder has been created.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809783
Thanks - from my questions above ...
sudo systemctl start systemd-rfkill
Is the folder then created? Retained after reboot?
If you purge the tlp package and check the status/start the systemd-
rfkill service and reboot what happens?
--
You received this bug notification because you are a
This is the output of "sudo systemctl status systemd-rfkill":
● systemd-rfkill.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead)
As you can imagine the /var/lib/systemd/rfkill folder hasn't been
created after running the command
--
You received this bug notification because
John
what is the output of
sudo systemctl status systemd-rfkill
?
When I run
sudo systemctl start systemd-rfkill
I see the folder /var/lib/systemd/rfkill created
After a reboot is that folder still there?
If you rerun
sudo systemctl status systemd-rfkill
Does it say after
Note also - a quick Google brought this up
https://major.io/2015/07/19/restoring-wireless-and-bluetooth-state-
after-reboot-in-fedora-22/
Just wondering if this is a TLP default config issue as per that article
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Daniel
gnome-settings-daemon I would suggest looking at the code.
Budgie Desktop itself wouldn't create that that systemd rfkill folder.
If Gsd isn't creating that folder is there another gnome package that
does? Maybe UB is missing a 0ackage that we can add to our seeds
--
You received this
Thanks. If the directory /var/lib/systemd/rfkill does not exist then
that would be why Bluetooth is always on when you reboot. Because the
flag which is used to indicate that it should be off (soft blocked) is
missing.
Next we need to find out what component should be telling rfkill to save
the
These are all rfkill directories I found:
./snap/core/6130/usr/share/doc/rfkill
./snap/core/6130/var/lib/systemd/rfkill
./snap/core/5897/usr/share/doc/rfkill
./snap/core/5897/var/lib/systemd/rfkill
./snap/core/6034/usr/share/doc/rfkill
./snap/core/6034/var/lib/systemd/rfkill
grep: / var / lib / systemd / rfkill / *: File or directory does not exist
Can't find "rfkill" directory under systemd.
These are all the other directories under systemd:
backlight coredumpdeb-systemd-helper-masked timers
catalogdeb-systemd-helper-enabled random-seed
Budgie is using the gnome-settings-daemon dbus
org.gnome.SettingsDaemon.Rfkill to toggle bluetooth on and off/send
files etc.
https://github.com/solus-project/budgie-
desktop/blob/master/src/applets/status/BluetoothIndicator.vala
--
You received this bug notification because you are a member of
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809783
Title:
Bluetooth always on when power on my laptop
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
23 matches
Mail list logo
