debcrafters-packages team mailing list archive

[Mitchell Augustin <2119741@xxxxxxxxxxxxxxxxxx>]

Hi Chris,

Thanks for reviewing.

"non-BDR/EDR device" here is just another way of saying "Bluetooth Low
Energy (BLE)" device.

I think a more precise description of the change would be that it
corrects the current behavior to ensure that BLE devices which are
already paired (and thus expect to auto-reconnect, from the user's POV)
actually do.

My interpretation of the source history with respect to this issue is
that
https://github.com/bluez/bluez/commit/507ba12483c3b6504d7fc0abfbbe1b4a0c8fa006
(which introduced the buggy behavior) changed the behavior for *all*
types of temporary connections, when it really should have only been
applied to BDR/EDR (Bluetooth Classic).
https://github.com/bluez/bluez/commit/39467578207889fd015775cbe81a3db9dd26abea
(our requested SRU patch) is what fixes that issue for BLE.

Let me know if you have additional questions!

-- 
You received this bug notification because you are a member of
Debcrafters 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