On Tue, Mar 28, 2017 at 07:59:02AM -0700, Mick wrote: > Mar 28 15:50:20 dell_xps bluetoothd[10619]: Unknown key AutoEnable in > main.conf
Did you use the 'AutoEnable' option in the '[Policy]' section of main.conf? > So, what's the solution if hciconfig et al are not installed with future > versions of bluez and the AutoEnable option does not seem to take? I'm pretty sure the future solution is to use bluetoothctl as a console user interface or find a more scriptable alternative (I don't know of any) that also use the DBus interface. I just hit this problem with the upgrade as I was using scripts to manage turning bluetooth on and off and I was able to get by with just the AutoEnable option. I did not find much else in my cursory research as to a replacement for hciconfig. The following is from the release notes for BlueZ 5.35: > A noteworthy new feature is the ability to configure bluetoothd to > automatically enable (power on) all new adapters. One use of this is to > replace unreliable "hciconfig hci0 up" commands that some distributions > use in their init/udev scripts. The feature can be enabled by having > AutoEnable=true under the [Policy] section of /etc/bluetooth/main.conf. Foster
