Hello developers, After migrating to new GNOME openrc, the state of the bluetooth daemon is not remembered across reboots. e.g. after turning bluetooth off, a reboot enables it again.
(In reply to spargeltarzan from comment #0) > Hello developers, > > After migrating to new GNOME openrc, the state of the bluetooth daemon is > not remembered across reboots. e.g. after turning bluetooth off, a reboot > enables it again. I don't see this as a gnome issue at all. The kernel will automatically bring the device on if you have support for it in the kernel.
(In reply to Jory A. Pratt from comment #1) > (In reply to spargeltarzan from comment #0) > > Hello developers, > > > > After migrating to new GNOME openrc, the state of the bluetooth daemon is > > not remembered across reboots. e.g. after turning bluetooth off, a reboot > > enables it again. > > I don't see this as a gnome issue at all. The kernel will automatically > bring the device on if you have support for it in the kernel. The issue wasn't in my previous GNOME systemd setup and I didn't change something it the kernel at all. Openrc reports the status of the service bluetooth as "on", although bluetooth is off. If I turn off the service bluetooth with openrc, I wouldn't be able to turn bluetooth on graphically in GNOME. When adding bluetooth to the runlevel, bluetooth is always on no matter if I turned off bluetooth graphically before a reboot. In systemd the behaviour was different, the service was of course always on, but when I turned off bluetooth in GNOME, bluetooth remained to be off for weeks - but of course the systemd service bluetooth was on. So I believe there is somewhere the state of the daemon saved in systemd and was set accordingly when booting the system.
I see this as a similar issue as for the screen brightness, I opened for this bug 682390.