Comment 8 for bug 1084364

This is a well-known bug. If you search for it on the Internet, it shows up everywhere.

The actual behavior varies according to what desktop one has installed. For instance, KDE uses Kwallet instead of gnome-keyring. The KDE daemon wipes the password field so that it must be reentered, but the behavior is otherwise identical.

I believe that network-manager back-ends make incorrect system calls when it cannot immediately connect with the current password. It does not know whether the password is missing or incorrect, if the connection is unavailable, if the connection was stopped due to a suspend, lock, or shutdown, or if the connection was temporarily lost.

Frequently suggested work-arounds include deleting the connection, rebooting the computer, or deleting the connection and rebooting the computer. These are stopgap measures and hacks at best.

It is also suggested that this is a driver issue, but for many the system is using the best or only network driver available. The obvious alternative is Wicd, but it has yet been updated to the long awaited version 2.0. The current version is simply not capable of making all types of modern wireless connections.