Ah! So my understanding of the current state is: BLE devices get passively picked up, and (correctly) get marked as “don't autoconnect”, because we *don't* want to autoconnect to every BLE device that happens to wander in range.
However, when we subsequently *pair* with that device, we (incorrectly) fail to remove the “don't autoconnect” mark - the user has now actively made a decision to connect to that device. This fix is doing the “remove the ‘don't autoconnect’ mark when the user explicitly pairs with a BLE device”. Is there any case in which a user would want to pair a BLE device and then expect it *not* to auto-reconnect? I can't really think of any plausible scenario. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2119741 Title: Bluetooth device does not reconnect after being paired To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2119741/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
