** Description changed: - Upstream patch: https://gitlab.gnome.org/MitchellAugustin/gnome-shell/-/commit/ae85e11ca198ade20b84cbd1f2660d1fc6203095 + Upstream patch: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3834 (currently being upstreamed, WIP) Impacts Noble, Plucky, Questing (Jammy's quicksettings menu uses a different view which this bug isn't applicable to.) SRU Justification: [ Impact ] network.js passes an incorrect variable type when attempting to connect to an enterprise AP from the quicksettings panel. This patch corrects this behavior, allowing the panel to be loaded. [ Test Plan ] 1. Set up a WPA or WPA2 access point. (You do not actually need a RADIUS server to reproduce the issue, since it occurs simply when trying to load the credential popup.) 2. On your test device, click the quick-settings menu, then expand the Wi-Fi AP list. Select your enterprise AP [ Fix ] Adjust the variable type in network.js to match what the gnome-settings panel and gnome-shell actually expect [ Where problems could occur ] There should be no regressions here, since prior to this patch, launchSettingsPanel() was passing an invalid variable type that was failing a broad gnome-shell assertion, halting the desired command from running. Other callers of launchSettingsPanel() may be impacted by this change (but I would actually suspect that they'd suffer from the same issue, so my patch may fix those cases as well if so)
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2120331 Title: [SRU] status/network: Fix connecting to WPA[2] Enterprise networks from quicksettings panel Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Jammy: Invalid Status in gnome-shell source package in Noble: In Progress Status in gnome-shell source package in Plucky: In Progress Status in gnome-shell source package in Questing: In Progress Bug description: Upstream patch: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3834 (currently being upstreamed, WIP) Impacts Noble, Plucky, Questing (Jammy's quicksettings menu uses a different view which this bug isn't applicable to.) SRU Justification: [ Impact ] network.js passes an incorrect variable type when attempting to connect to an enterprise AP from the quicksettings panel. This patch corrects this behavior, allowing the panel to be loaded. [ Test Plan ] 1. Set up a WPA or WPA2 access point. (You do not actually need a RADIUS server to reproduce the issue, since it occurs simply when trying to load the credential popup.) 2. On your test device, click the quick-settings menu, then expand the Wi-Fi AP list. Select your enterprise AP [ Fix ] Adjust the variable type in network.js to match what the gnome- settings panel and gnome-shell actually expect [ Where problems could occur ] There should be no regressions here, since prior to this patch, launchSettingsPanel() was passing an invalid variable type that was failing a broad gnome-shell assertion, halting the desired command from running. Other callers of launchSettingsPanel() may be impacted by this change (but I would actually suspect that they'd suffer from the same issue, so my patch may fix those cases as well if so) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2120331/+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
