+++ This bug was initially created as a clone of Bug #215601 +++ Description of problem: Should be able to tell NM to try the previously saved passphrase, as it may be failing its connection because the type of encryption changed, and not because the passphrase did. Or, because the WAP wasn't fully up from reboot yet. Version-Release number of selected component (if applicable): NM-0.6.4-5.fc6 How reproducible: Always Steps to Reproduce: 1. Reconnect to a previously connected WAP which had a passphrase or shared key, but which changed its type of encryption, or was recently rebooted. Actual results: It will ask you to enter the passphrase or shared key again, even though it's the same as it was before. Expected results: Ask for details about the connection, but have something to check which tells it that the passphrase did not actually change. Additional info:
Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
Connection info including passwords are now prefilled in the dialog. Closing.