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 455737 - NetworkManager cannot connect to unencrypted wireless networks
NetworkManager cannot connect to unencrypted wireless networks
Status: RESOLVED DUPLICATE of bug 372124
Product: NetworkManager
Classification: Platform
Component: general
0.6.6
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2007-07-10 23:11 UTC by Ian Malone
Modified: 2008-08-08 21:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ian Malone 2007-07-10 23:11:17 UTC
+++ This bug was initially created as a clone of Bug #324660 +++

Please describe the problem:
Network manager times out when connecting to an unencrypted wireless network if that network was previously encrypted.

Steps to reproduce:
1. Enable WPA on router, switch on laptop and connect using NM.
2. Disable NM wireless (Killing connection)
3. Disable WPA on router
4. Re-enable NM wireless

Actual results:
NM times out at step 4. and fails to connect.

Expected results:
NM sucesfully connects to network.

Does this happen every time?
Apparently.  Running NM as root from command line for debug
caused the problem to skip an iteration (could successfully
connect to the open net on first try, but not subsequent
attempts).  Certainly further attempts to connect fail until
WPA is re-enabled.

Other information:
Output from --no-daemon filed comment #5:
* http://bugzilla.gnome.org/show_bug.cgi?id=324660
* Changing ESSID allows connection to open network on the
new ESSID.

Related bug? Filed at Fedora (seen on x86 and x86_64):
* https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242469 
* I have also seen NM fail to associate with open nets the
first time it encounters them, still need to test whether
this was the driver's fault.

Sorry for cloning this one, but the previous bug was marked
closed/incomplete when I first filed to it and seemed to be
unseen.
Comment 1 Germán Poo-Caamaño 2008-08-08 21:55:14 UTC
It seems whenever some settings changes in the AP, NM can't reconnect.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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