blueman: 2.0.8-1
BlueZ: 5.50-1+b1
Distribution: ParrotOS/Debian
Desktop environment: KDE
Hi. Spent couple hours today on trying to get why blueman start's bluetooth on boot, though I have AutoEnable=false in /etc/bluetooth/bluetooth.conf. So far I understood that blueman has default:true for PowerManager plugin. I think it should get the AutoEnable property via dBus because it basically overrides this option, even if you have AutoEnable=false blueman with turned on PowerManager will register the device, which is actually not supposed to be.
I guess every other plugin also has the "default" values which actually have to be sent with bluez via dbus.
[x] I have consulted the Troubleshooting page and done my best effort to follow.
blueman: 2.0.8-1 BlueZ: 5.50-1+b1 Distribution: ParrotOS/Debian Desktop environment: KDE
Hi. Spent couple hours today on trying to get why blueman start's bluetooth on boot, though I have AutoEnable=false in
/etc/bluetooth/bluetooth.conf. So far I understood that blueman has default:true for PowerManager plugin. I think it should get the AutoEnable property via dBus because it basically overrides this option, even if you have AutoEnable=false blueman with turned on PowerManager will register the device, which is actually not supposed to be.I guess every other plugin also has the "default" values which actually have to be sent with bluez via dbus.