Yes, Quantal doesn't connect and must be manually connected through system settings, even though it remembers the network name, encryption, etc. When it boots up, where it should connect, it says "disconnect" which does show up in the many many messages from network manager on the syslog. Once network manager (or the kernel, I wouldn't know) asks for authenticate it goes right through.
Since Raring is all setup to recognize hidden wireless, the network, and the encryption key it should try that first off. Instead it seems to do a knee jerk disconnect and then never even tries to connect with the information it already has. Where is the spot in the nm script that says go do the connect and authenticate? Why isn't it being issued? Let me go check Precise again. I usually run Raring but do have backup Quantal and Precise partitions. Thanks for looking at this. -- 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/network-manager/+bug/1097002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
