Ok, there seems to be another problem I didn't respected yet. Powering a controller with hciconfig will bring it into a state where not all subsystems are initialized required for LE support. We still have a udev rule in our bluez package included which will try to power a bluetooth controller via hciconfig which is really not what we should do as described before. Starting with bluez 5.35/.36 there is a new option bluez itself provides for this which defines a config element in /etc/bluetooth/main.conf to do the same but the right way.
I am not sure if this udev rule comes into our way here but it feels a bit like it does. @Pat/Tony: Would be good if you can try the following: sudo mount -o remount,rw / sudo rm /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules echo "[Policy]" >> sudo tee -a /etc/bluetooth/main.conf echo "AutoEnable=true" >> sudo tee -a /etc/bluetooth/main.conf I've also pushed this change up at https://code.launchpad.net/~bluetooth/bluez/fix-ctrl-enablement-on- detection as that is something we need to fix anyway. If that doesn't help also try removing all bluetooth state information by sudo rm -rf /var/lib/bluetooth/* and then reboot the device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1531925 Title: Can't connect Logitech Living Room Keyboard [LE] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
