Comment 34 for bug 1017738

Marius, I've tried upstream Debian kernel. Same problem.
Analysis from upstream was when the authentication was presented to the kernel, the kernel connected no problem right away.
This is evident in the syuslogs where the syslog shows once the authentication request gets around to being issued, connection goes normally.

Precise works fine. It's not an installation problem. If it was installation then Precise would have the same problem. It does not. Do note, the Network Manager used by Precise is not the same as Quantal.

The problem does occur with Quantal CD live, and has since the first daily builds that I can remember, and also with Raring.

The following syslog lines shows wlan0 is ready but then nm disconnects it?? Why? Why is "available" a reason to disconnect?

Oct 31 19:30:18 Aspire1 NetworkManager[888]: <info> (wlan0): supplicant interface state: starting -> ready
Oct 31 19:30:18 Aspire1 NetworkManager[888]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Oct 31 19:30:18 Aspire1 NetworkManager[888]: <warn> Trying to remove a non-existant call id.
Oct 31 19:30:18 Aspire1 NetworkManager[888]: <info> (wlan0): supplicant interface state: ready -> inactive
Oct 31 19:30:18 Aspire1 NetworkManager[888]: <info> (wlan0) supports 5 scan SSIDs

Thanks for any ideas. Jerry