Comment 20 for bug 1097002

Raring Ringtail on every boot (with U+1 I do a lot of boots) does not automatically connect to WPA wireless.
Raring Beta 2 invariably "disconnects" on boot. Systems Settings Network says "out of range" obviously tried to connect without the encryption key it already has. Manually select drop down window, shows the correct network, select it, and after a while presents a drop down with all the required info, and waits for me to select it. I do, and after a while it connects. Syslog has some network manager messages about "secrets required" and is oblivious to the "secrets" network manager already has.

Pangolin on the same pc and netowrk connects autmatically, might take a couple seconds. Raring doesn't connect, as a matter of Network Manager policy.

Android tablets on the same network (7" and 10.1") set up encryption once and they connect immediately. Every time. Raring doesn't.

Chromebook boots, zooms up, connects, and bam into the internet. Once encryption is set up always boots right up, using the info, no manual intervention required. Raring doesn't compete with Chromebook on boot and ease of getting to internet.

Apparently Network Manager doesn't consider this a bug, just the way network manager has decided to slow down boot. My other wireless products are set up for user convenience.