3 things: 1) Connecting to my FON insecure signal does work (so it might be that).
2) I've noticed that a few times it has connected successfully. I forgot to mention that in the original report because it is so rare, sorry. However, by far the majority of times it does not connect and I get the symptoms described. If you take a look at the partial syslog I attached initially you'll see what usually happens. Once other thing, since the most recent nm update a few days ago things have changed slightly. 1) Now the nm icon often doesn't appear in the status bar (but it still connects to the insecure signal). 2) Now when I goto 'edit connections' or am prompted to enter my wifi password the box is now empty, rather than filled with the long key I posted above. 3) Also keys are no longer saved in seahorse at all (i.e. if I choose not to save as a system setting. Perhaps this is the reason for [2], above?) 4) Finally, if I do choose to save as a system setting, and I navigate to etc/NetworkManager/system-settings, I can find a file in there which has successfully saved the connection. But when I open the file I find on the key/password line the dreaded "5eea414a9785dd... etc." instead of my actual password. -- [intrepid] network manager repeatedly asks for key, cannot connect to secured networks https://bugs.launchpad.net/bugs/265127 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
