After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 734681 - If I'm already connected to a network, don't pop up an authentication dialog
If I'm already connected to a network, don't pop up an authentication dialog
Status: RESOLVED DUPLICATE of bug 665680
Product: gnome-shell
Classification: Core
Component: general
3.13.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-08-12 16:58 UTC by Elad Alfassa
Modified: 2015-07-14 23:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Elad Alfassa 2014-08-12 16:58:17 UTC
This is a problem I've been having for a while.

Due to the way wpa2 works, you can't really know if you failed to authenticate or if the AP is not responding to your attempts.

Sometimes, when the signal goes weak enough (bad weather, electromagnetic interference, AP overheating, etc etc) the system thinks the network was disconnected. It tries to reconnect, but the AP doesn't reply, so it pops up a modal dialog asking for the password again - it thinks my password was wrong.

That's a bad thing. System modal dialogs should never spontaneously pop up. In that dialog, I already have my password saved, so I just click connect, and in most cases it makes the network work again, and sometimes if I do it fast enough my connections don't die and such.

If I'm already connected to a network (so we know the password works) there's no need to ask me for the password again, and especially not in a system modal dialog that distracts me from what I'm doing and grabs keyboard focus.

I know I'm not the only one who has this problem because several people have mentioned it in GUADEC.
Comment 1 Alexandre Franke 2015-07-14 23:11:12 UTC

*** This bug has been marked as a duplicate of bug 665680 ***