I agree that this is very inconvenient. For example, I have a system at home that I leave unattended but I need it to reconnect automatically to my wifi, because I need to access it from abroad. If there is a disconnect and it can't reconnect immediately (e.g., because of a router reboot), the password dialog will prevent network manager from connecting to my wifi again, effectively killing my access to this machine.
So I would say that even if network manager needs to ask for the password because it can't know whether the password is correct, this should not block all other operations: network manager should try connecting to the wifi in the background (and if it succeeds, hide the dialog). This is also asked here: https://bugzilla.gnome.org/show_bug.cgi?id=680625 Maybe https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1407907, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1316634 and https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1010745 are related? Users have requesting this since 2010: http://askubuntu.com/q/19137/51272 ** Bug watch added: GNOME Bug Tracker #680625 https://bugzilla.gnome.org/show_bug.cgi?id=680625 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1633413 Title: Obsolete authenthication requests for WiFi Status in network-manager package in Ubuntu: Confirmed Bug description: When a WiFi connection behaves unstable over longer time (eg. long range), sometimes the user is asked for the password again (the requester come up already filled), even if it is correct. The request can come up at any time, depending on the connection quality, and likely force the user to look up the already correctly entered password again. This is very annoying for kiosk-like systems or when using fullscreen apps. This bug is stone old and iv'e seens this year by year over a broad range of Ubuntu versions as well devices (Intel and ARM platform). It still happens as of Ubuntu 16.04. So I wonder if this is inevitable by the fact that NetworkManager sometimes can't decide between an authetication failed by wrong password vs. authentication failed by bad connection. If not, it should finally be fixed. There may be a security problem, for locked down kiosk applications, as the password may be obtained by kiosk users if the request pops up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
