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 740746 - Wi-Fi password dialog pops up without invitation
Wi-Fi password dialog pops up without invitation
Status: RESOLVED DUPLICATE of bug 660293
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-11-26 12:32 UTC by Allan Day
Modified: 2014-11-26 13:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Allan Day 2014-11-26 12:32:18 UTC
I have a docking station with a wired network connection. While I am using it, I regularly get Wi-Fi password dialogs popping up (this is GNOME 3.14/Fedora 21).

The situation is odd, because my password is known, and my laptop has no problems connecting when I am in other parts of the house. I suspect that it is because the Wi-Fi signal is weak where the docking station is...

But that's not the point - a dialog like this should only ever appear after the user manually tries to connect to a network. So:

 * If the primary route isn't Wi-Fi, allow it to fail silently if a connection drops or can't be established.

 * If Wi-Fi is the primary route and the connection drops or can't be established, use a notification to inform the user - don't pop up a dialog.
Comment 1 Dan Winship 2014-11-26 13:10:23 UTC
NetworkManager does not directly control any UI in GNOME 3.x.

We added a flag a while back that lets ShellNetworkAgent distinguish user-initiated requests from autoconnect requests, but the shell was never updated to use it.

*** This bug has been marked as a duplicate of bug 660293 ***
Comment 2 Allan Day 2014-11-26 13:13:29 UTC
Thanks Dan, and sorry for the noise.
Comment 3 Allan Day 2014-11-26 13:17:33 UTC
Seems like this is a dupe of bug 726764, not 660293, btw.