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 597889 - Network Connections: Incorrectly asks for pas...
Network Connections: Incorrectly asks for pas...
Status: RESOLVED DUPLICATE of bug 680625
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
: 627234 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-10-09 10:14 UTC by Johannes Berg
Modified: 2014-04-25 15:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description Johannes Berg 2009-10-09 10:14:13 UTC 
Incorrectly asks for passphrase

If associating to a WPA network fails, e.g.

[   90.925451] wlan0: direct probe to AP 00:06:25:ff:8f:78 (try 1)
[   91.068600] wlan0: direct probe responded
[   91.068607] wlan0: authenticate with AP 00:06:25:ff:8f:78 (try 1)
[   91.260073] wlan0: authenticate with AP 00:06:25:ff:8f:78 (try 2)
[   91.460076] wlan0: authenticate with AP 00:06:25:ff:8f:78 (try 3)
[   91.670068] wlan0: authentication with AP 00:06:25:ff:8f:78 timed out


then NM will still ask the user to verify that the passphrase is correct. It should only do that when the WPA handshake fails, but the association was successful.


Distribution: Debian squeeze/sid
Gnome Release: 2.28.0 2009-09-27 (Debian)
BugBuddy Version: 2.28.0
Comment 1 André Klapper 2012-06-10 01:40:58 UTC 
*** Bug 627234 has been marked as a duplicate of this bug. ***
Comment 2 Pavel Simerda 2012-07-26 13:41:02 UTC 
Old bug. Is this still the case with 9.x?
Comment 3 Johannes Berg 2012-07-26 13:43:07 UTC 
no idea, haven't seen it again but haven't used encrypted networks in bad conditions either
Comment 4 Pavel Simerda 2012-07-26 23:07:40 UTC 
Thanks. Closing for now.
Comment 5 Matthew Paul Thomas (mpt) 2014-04-25 15:53:40 UTC 

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