debcrafters-packages team mailing list archive
-
debcrafters-packages team
-
Mailing list archive
-
Message #05818
[Bug 2119741] Re: Bluetooth device does not reconnect after being paired
Thanks for the verification.
Could you please just clarify exactly the package that you used when
carrying out the test plan? As per SRU instructions from comment #12:
"If this package fixes the bug for you, please add a comment to this
bug, mentioning the version of the package you tested, what testing has
been performed on the package and change the tag from verification-
needed-noble to verification-done-noble."
This may seem unnecessary, but there have been cases in the past where
the test plan was mistakenly carried out with a local package build, or
from a PPA, instead of the proposed pocket, meaning that what was tested
was not what was eventually delivered to users via updates.
--
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:
Fix Committed
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
References