Comment 38 for bug 912702

NetworkManager itself appears to be resetting the number of retries for *all* "failed" connections regardless of what the cause for failure was, even if that failure was caused by missing secrets (what seems to be causing the prompt for entering the password again).

Now, this particular issue can come from buggy drivers which would pass the secret wrong or otherwise fail to connect to an access-point with an unusual or plain incorrect return code. We can't really account for these without special casing each driver. However, I was able to reproduce the issue and write a patch that seems to properly fix the authentication cases where the password in "incorrect" in NM or otherwise refused by the AP. When a connection fails because of missing secrets (e.g the user was prompted but never answered), the connection is properly marked as failed; then, after 5 minutes the connections that are failed because of "missing secrets" don't have their retries set back to 0 like the other failed connections, but rather will wait until an agent registers, at they should.

There is a test package being built at https://launchpad.net/~mathieu-tl/+archive/ppa/+sourcepub/3776171/+listing-archive-extra (my PPA). Please give it a shot and let me know if this fixes the issue acceptably.