As of 23 January, Raring still disconnects. Sees the hidden wireless network.
NM reports that "secrets required" so it disconnects. Then NM discovers it has the "secrets" i.e. the encryption password. Does not even try to connect. Pangolin, Mint14, etc. have no problem. Raring's NM won't connect at boot, Manually, select the network which is displayed, NM says "out of range". It is not out of range. NM tried to connect without using the "secret" password, which of course won't work don't even try it, then falsly concluded must have been out of range. Manually select connect to hidden network. NM magically fills in all the "secrets" which it had stored. Manually connect just fine. It is not "out of range". The NM logic for connecting is wrong. 1. If the network that has been set up is a hidden encrypted network, don't even try to connect without the encryption key. That's the mistake in the NM logic. 2. Since it's the same network I always use, do connect on every boot, using the already stored encryption key. I"m set up to connect automatically, then do it. Any suggestions on how to "connect automatically"? In development, with unstable Raring, I boot a lot. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097002 Title: On every boot, raring 3.7.0-7 fails to connect to wireless WPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
