https://bugs.kde.org/show_bug.cgi?id=440493
--- Comment #4 from Nate Graham <n...@kde.org> --- I did some investigation. Looking through the source code at https://git.kernel.org/pub/scm/bluetooth/bluez.git/, it would appear that this AutoEnable option is only accessible through the global config file in /etc. There is no option to toggle it at runtime or override a default value in that file with a file in your homedir; in principle this does not make sense anyway since the adapter would already have to be on or off by the time you log in and your homedir becomes accessible. However we can't add a config UI that alters the contents of /etc/bluetooth/main.conf, because that's a distro-provided file, so the changes would simply get overridden with every upgrade to the package that provides it. What we would need is for the feature to dynamically install and remove a package that installs a config file with this property set to true; the default is false, so not having it means the bluetooth adapters do not automatically power up on boot. However this would be dependent on distro packaging. On openSUSE for example, we could install and remove the bluez-auto-enable-devices package. However Fedora provides no such package, and instead simply unconditionally enables the bluetooth adapters by default. Other distros no doubt do other things. Needless to say, implementing the kind of package installer/uninstaller functionality in the KCM that would be necessary to make this wotk would be fragile due to distros changing package names, changing defaults, etc. It would be doable, but messy and incomplete as support would have to be added to every distro that does not currently ship a config file in a package the way openSUSE does. I'm not sure this will be possible to do. :/ Unless you or someone else can think of a smarter option that what I outlined above, this may sadly have to be a RESOLVED CANTFIX. :( -- You are receiving this mail because: You are watching all bug changes.
