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 661208 - asks for wireless passphrase twice
asks for wireless passphrase twice
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2011-10-07 17:23 UTC by Bill Nottingham
Modified: 2014-01-02 17:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bill Nottingham 2011-10-07 17:23:37 UTC 
1. Have a WPA or similar network
2. Have it not connect for whatever reason
3. Get shell 'please enter passphrase' dialog
4. Hit cancel
5. Get nm-applet 'please enter passphrase' dialog

Step 5 shouldn't happen.

NetworkManager-gnome-0.9.1.90-3.git20110927.fc16.x86_64
gnome-shell-3.2.0-2.fc16.x86_64
Comment 1 Giovanni Campagna 2011-10-08 14:54:20 UTC 
Step 5 shouldn't happen for two reasons:

1) nm-applet should not be running in a shell session, just in the fallback
2) NetworkManager should not ask an other agent for the same session/user if the first reported USER_CANCELED.

Even if we accept that 1 is a sort of known bug in 3.2 (we need nm-applet for VPN), I think 2 is a NetworkManager bug.
Comment 2 Cosimo Cecchi 2011-10-24 22:38:23 UTC 
Confirming on 3.2.1.
Giovanni: is 2) a known NM bug? (as in, was it reported?)
Comment 3 Giovanni Campagna 2011-10-25 06:46:05 UTC 
(In reply to comment #2)
> Confirming on 3.2.1.
> Giovanni: is 2) a known NM bug? (as in, was it reported?)

To be honest, 2) is not a real bug, in the sense that there should not be two agents for the same user/session. gnome-shell 3.2 is a sort of edge case in this regards, and hopefully nm-applet will be obsoleted in 3.4

In any case, reassigning to NetworkManager, so that Dan can decide if it's worth fixing there as well.
Comment 4 hotani 2012-07-16 15:34:20 UTC 
(In reply to comment #0)
> 1. Have a WPA or similar network
> 2. Have it not connect for whatever reason
> 3. Get shell 'please enter passphrase' dialog
> 4. Hit cancel
> 5. Get nm-applet 'please enter passphrase' dialog
> 
> Step 5 shouldn't happen.

How about step 3 shouldn't happen? Instead there should be a notification that the connection failed and would you like to retry. At no point in this process should anything be asking for passphrases. 

I get the double passphrase problem as well when my wifi is being finicky. It makes the system unusable because it won't shut up and keeps blocking the screen with dialog boxes asking for passphrases. Hitting Cancel doesn't stop them.

System: Debian Testing/ GNOME 3.4
Comment 5 Dan Winship 2014-01-02 17:00:29 UTC 
old bug, fixed now