Ok, I did some investigation and looked at syslog for a succesfull and two failing BT reconnects. This is the succesful log (the others will follow). A quick scan over the lines reveals one outstanding difference between success and failure:
On failure, NetworkManager reports this extra line, which is completely missing from succes log upon receiving the "new Bluetooth device message". Oct 24 11:15:51 minivanes NetworkManager[828]: <info> [1477300551.0193] device (60:51:2C:A2:05:CC): state change: disconnected -> unmanaged (reason 'removed') [30 10 36] After enabling bluetooth in plasma bluetooth interface, the two failed syslog's final conclusions are: Oct 24 11:22:05 minivanes NetworkManager[828]: <info> [1477300925.4564] device (60:51:2C:A2:05:CC): state change: unavailable -> disconnected (reason 'none') [20 30 0] So, in short: On failing resumes NetworkManager incorrectly concludes the BT is unmanaged, instead of just disconnected. Which is exactly the last line for a succesful resume. ** Attachment added: "Succesful resume" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635157/+attachment/4766822/+files/BT_succes.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635157 Title: Bluetooth disabled after resume from standby on Yakkety (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635157/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
