I think the original issue seems to be fixed. If you still see a similar issue check i nsyslog whether the connect fails. If thats the case NM re-asks for a password as it assumes that it might be wrong - especially when using wep encryption NM cannot tell whether password is wrong or you just got a driver/network timeout.
I think the original issue seems to be fixed. If you still see a similar issue check i nsyslog whether the connect fails. If thats the case NM re-asks for a password as it assumes that it might be wrong - especially when using wep encryption NM cannot tell whether password is wrong or you just got a driver/network timeout.