In the case of wicd it was found that wpa_supplicant routinely timed out before a WiFi connection has been completed successfully. This triggered endlessly repeated wicd connection attempts, each time resulting in an erroneous and misleading "BAD PASSWORD" error message. Increasing the value of the time-out parameter governing wpa_supplicant appears to have resolved this issue in wicd.
In the case of network manager, quite possibly a similar time-out for wpa_supplicant triggers the repeated popping up of the panel requesting the WPA2 authorization password even though this password is already known to network manager.
An issue with wicd (an alternative to network manager) which is possibly related to the issue reported here has been reported at: https:/ /bugs.launchpad .net/wicd/ +bug/1084380
In the case of wicd it was found that wpa_supplicant routinely timed out before a WiFi connection has been completed successfully. This triggered endlessly repeated wicd connection attempts, each time resulting in an erroneous and misleading "BAD PASSWORD" error message. Increasing the value of the time-out parameter governing wpa_supplicant appears to have resolved this issue in wicd.
In the case of network manager, quite possibly a similar time-out for wpa_supplicant triggers the repeated popping up of the panel requesting the WPA2 authorization password even though this password is already known to network manager.