Hello Leo, or anyone else affected, Accepted gnome-bluetooth3 into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- bluetooth3/46.0-1ubuntu1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. 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. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2081672 Title: Scanning not enabled by the Bluetooth slider Status in OEM Priority Project: New Status in gnome-bluetooth3 package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-bluetooth3 source package in Noble: Fix Committed Status in gnome-bluetooth3 source package in Oracular: Fix Committed Bug description: [ Impact ] * Turning off bluetooth for over 1 minutes and turn on it in bluetooth panel. There is no devices list, and the bluetooth controller is not discoverable. [ Test Plan ] * Find a machine with bluetooth as the device under test (DUT) * Open g-c-c bluetooth panel on the DUT * Turn off the bluetooth on the DUT for 1 minutes * Put another bluetooth gadget to discovery mode * Turn on the bluetooth on the DUT in the bluetooth panel * There should be bluetooth device listed, and the DUT is also discoverable [ Where problems could occur ] * The change capture the situation that the dicoverable flag is being set wrongly, so that the application is not able to trigger scan anymore. The issue might still happen if the adapter not able to be in powered state, but it is not the situation that the patch is trying to fix. [ Other Info ] * Upstream, https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/commit/de707f592304309a59208e3ed1afbe4a37568bdd https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/commit/3d45205c79b48dd3e15e1c4edb58cf8cd79f23ef To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2081672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
