Hi, Just got home and tried again and has similar issues. I've attached the syslog. I waited a couple of minutes between resuming the laptop and entering in the screen-saver password to see if that made a difference. It appears from the log that when it fails to connect to the AP it assumes that the key is wrong rather than that the AP is no longer there and prompts for a new key. In this case I cancelled the key and it then appears it tries to connect to the next AP in the list which is my work list and attempted to connect to "absa_connectivity1" (or something) I then selected the correct AP from the list and successfully connected to that.
One possible solution would be to rescan for APs on resume and then attempt to connect to the known networks it can now find. This might slow down reconnection to the same AP if you just suspend the machine and try and reconnect on resume. It might be an option to have a quick reconnect option that will use the current behaviour where it tries to reconnect to the same AP on resume if you hardly ever connect to other APs but if you do like I do, one at work and one at home a rescan option might be preferable. Ray ** Attachment added: "syslog.out.4.gz" http://launchpadlibrarian.net/22556987/syslog.out.4.gz -- network-manager unreliable with multiple APs https://bugs.launchpad.net/bugs/111502 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
