Bugzilla – Bug 262183
NetworkManager "remembers" bad wireless settings
Last modified: 2007-10-19 10:57:27 UTC
If I try to configure my wireless security settings with NetworkManager, and the connection fails, and I select the same network to connect to again, it doesn't give me a chance to edit the settings. So it fails again. Under 10.2, my recollection is that it always came up with a blank settings screen if the previous attempt failed to connect. To me, it would be ideal if it brought the security settings screen up again, but with the previous values populated as defaults (perhaps leaving the passphrase blank if that's a security concern). As it is now, I seem to have to log out and log back in again in order to be able to change the settings and try again.
Oops, I just noticed that this was assigned to the GNOME team and I neglected to mention that I'm using KDE and KNetworkManager. Not sure if it makes a difference.
Here the network manager doesn't remember it was configured to use a static adress (and uses dhcp instead). Maybe that's related to the above mentioned bug... But it works fine if i use the "traditional" ifup-method...
I believe its up to the knetworkmanager front end to store/re-ask the credentials.
Helmut, can you please comment? Thanks!
> To me, it would be ideal if it brought the security settings screen up again, > but with the previous values populated as defaults (perhaps leaving the > passphrase blank if that's a security concern). That's how it works for me. Aaron, can you please give a bit more information on how to reproduce this issue? Can you please attach /var/log/NetworkManager? Thanks
Aaron, any news on this topic? Did you try with a 10.3 beta yet?
Closing this one as FIXED as it is most likely fixed in 10.3. Please reopen if you experience the same problems in 10.3.