** Description changed: [ 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 patch is adding a case where the device discovery will not be - enabled. If the condition was wrong the discovery state could be changed - incorrectly, leading to the computer not getting visible nor listing - other devices when it should or in the reverse way, being listed by - other devices when it shouldn't. In practice the computer should only be - available to other devices when the toggle is enable and the setting - panel displayed. + * 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
-- 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 Committed Status in gnome-control-center package in Ubuntu: Invalid 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
