Public bug reported: SRU Justification:
[ Impact ] UX inconsistency - users are unable to enter the password for protected wi-fi networks when attempting to connect via quicksettings on the lock screen, whereas the can successfully connect to an open network. Steps to repro: 1. After logging in, lock the screen and don't log back in 2. Try to connect to a password protected AP on the top right gnome settings that displays available WiFi networks 3. Try to connect to an open AP (no password) on the top right gnome settings that displays available WiFi networks Expected Results: 1. Behavior is consistent - either this connectivity is not allowed for any networks, or users can connect to open and closed networks (i.e., the password prompt for the network displays). Actual results: 1. When trying to connect to password protected AP, there is no password pop-up and cannot connect to it 2. When trying to connect to an open AP, the connection is successful without logging in [ Test Plan ] 1. After logging in, lock the screen and don't log back in 2. Try to connect to a password protected AP on the top right gnome settings that displays available WiFi networks 3. Try to connect to an open AP (no password) on the top right gnome settings that displays available WiFi networks [ Fix ] Enable the networkAgent within the unlock-dialog in sessionMode. This ensures that selecting a password-protected Wi-Fi network in quicksettings behaves the same on both the initial gdm screen (before any user has logged in, as enabled already in 4440a821[0]) and when the screen has been locked by an already logged-in user. [ Where problems could occur ] If there are any side-effects from having the networkAgent enabled once gnome-shell is in this state, that could cause unexpected behavior - however, I expect that any such bugs would have already been visible/reported once [0] was merged, given that it enables the exact same functionality on the initial user login screen. [ Other Info ] [0] https://gitlab.gnome.org/GNOME/gnome- shell/-/commit/4440a8210b456923678facd434ef8a23d48f63b6 ** Affects: gnome-shell (Ubuntu) Importance: Low Assignee: Mitchell Augustin (mitchellaugustin) Status: In Progress ** Affects: gnome-shell (Ubuntu Noble) Importance: Low Assignee: Mitchell Augustin (mitchellaugustin) Status: In Progress ** Affects: gnome-shell (Ubuntu Questing) Importance: Low Assignee: Mitchell Augustin (mitchellaugustin) Status: In Progress ** Affects: gnome-shell (Ubuntu Resolute) Importance: Low Assignee: Mitchell Augustin (mitchellaugustin) Status: In Progress ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin) ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress ** Also affects: gnome-shell (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Questing) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Resolute) Importance: Low Assignee: Mitchell Augustin (mitchellaugustin) Status: In Progress ** Changed in: gnome-shell (Ubuntu Questing) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu Noble) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu Questing) Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin) ** Changed in: gnome-shell (Ubuntu Noble) Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin) ** Changed in: gnome-shell (Ubuntu Questing) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Noble) Status: New => In Progress ** Description changed: SRU Justification: [ Impact ] + + UX inconsistency - users are unable to enter the password for protected + wi-fi networks when attempting to connect via quicksettings on the lock + screen, whereas the can successfully connect to an open network. Steps to repro: 1. After logging in, lock the screen and don't log back in 2. Try to connect to a password protected AP on the top right gnome settings that displays available WiFi networks 3. Try to connect to an open AP (no password) on the top right gnome settings that displays available WiFi networks Expected Results: 1. Behavior is consistent - either this connectivity is not allowed for any networks, or users can connect to open and closed networks (i.e., the password prompt for the network displays). Actual results: 1. When trying to connect to password protected AP, there is no password pop-up and cannot connect to it 2. When trying to connect to an open AP, the connection is successful without logging in [ Test Plan ] 1. After logging in, lock the screen and don't log back in 2. Try to connect to a password protected AP on the top right gnome settings that displays available WiFi networks 3. Try to connect to an open AP (no password) on the top right gnome settings that displays available WiFi networks [ Fix ] Enable the networkAgent within the unlock-dialog in sessionMode. This ensures that selecting a password-protected Wi-Fi network in quicksettings behaves the same on both the initial gdm screen (before any user has logged in, as enabled already in 4440a821[0]) and when the screen has been locked by an already logged-in user. - [ Where problems could occur ] If there are any side-effects from having the networkAgent enabled once gnome-shell is in this state, that could cause unexpected behavior - however, I expect that any such bugs would have already been visible/reported once [0] was merged, given that it enables the exact same functionality on the initial user login screen. [ Other Info ] [0] https://gitlab.gnome.org/GNOME/gnome- shell/-/commit/4440a8210b456923678facd434ef8a23d48f63b6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2147661 Title: [SRU R/Q/N] Wi-Fi password dialog does not appear via quicksettings connections on post-login lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2147661/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
