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 Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2119741 Title: Bluetooth device does not reconnect after being paired Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: Invalid Status in bluez source package in Noble: Incomplete Status in bluez source package in Plucky: Fix Released Status in bluez source package in Questing: Fix Released Bug description: [ Impact ] * Bluetooth mouse does not reconnect after turning bluetooth off and on on the ubuntu machine after pairing the device. * If you forget the device and re-pair it, it works until the next bluetooth disconnect. [ Test Plan ] * Make sure the device is not already paired * Pair it, move the mouse. It should work. * Turn off bluetooth and turn it back on. * The device should reconnect when used. [ Where problems could occur ] * The change modifies that each paired non BR/EDR device gets autoconnect set to true. This could lead to devices which were not autoconnecting before, to autoconnect now when they are re-paired. [ Other Info ] * This issue is already patched in questing and plucky * We were unable to reproduce the issue using jammy bluez version * This is a fix by including https://github.com/bluez/bluez/commit/39467578207889fd015775cbe81a3db9dd26abea from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2119741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
