Hi! In a GNOME default configuration: - where gdm is customized to autologin a particular user - the default keyring of this user has a blank password so it is automatically unlocked at startup - the password required to activate a wireless connection is available in the keyring, correctly defined with nm-connection-editor or gnome-control-center network, and visible with seahorse - Network-Manager is configured to ask the password to the network agent, confirmed by the 802-1x.password-flags property of this connection: value=1 meaning agent-owned - Network-Manager is configured to automatically connect using this connection setup. The dialog "Authentication required by wireless network" still appears at login time, with the username and password pre-filled, and validating this dialog is a requirement for the connection to successfully complete. Changing the connection password-flags value to zero, so the password is stored in the network-manager system-connections config file, instead of the user's keyring is a possible workaround, but editing this connection again with nm-connection-editor at a later time will revert this tweak to its default value (agent-owned). I think gnome-shell's network agent shouldn't request the password in this case, as it has all the available information to not do it.
The network agent should only pop up a dialog when requested by NetworkManager via DBus, so this might rather be an nm issue. Dan?
Hi, Same here fedora 20 x86_64 up-to-date (except I don't have autologin with a blank password but a classic user who enter a password at login)
I can confirm this also in the case with a normal password-protected user account, and a simple WPA2-PSK Wi-Fi connection configured through nm-connection-editor to NOT be available to other users (i.e., secret stored only in login keyring). I'm presented with a "Authentication required by wireless network" box every time I attempt to connect (with the correct password is already filled in).
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.