Jason: I'll make sure I'll add that command, just to be on the safe side.
Leo: it seems to be like a problem in wpa_supplicant really: as you can see, when the connection succeeds you have "WPA_CLI RESULT IS COMPLETED", while you don't have that in all other cases.
I guess wpa_supplicant it's taking more time than usual to finish association.
You could try increasing the time it tries -- it's currently set to 35 seconds. Open wicd/wnettools.py, and look for MAX_TIME, and set it to, say, 60. If that solves the issue (i.e. you find a "WPA_CLI RESULT IS COMPLETED" in the log), then we need to find out why wpa_supplicant takes so long to complete (and maybe it could be a good idea letting the user set that timeout from the GUIs).
Jason: I'll make sure I'll add that command, just to be on the safe side.
Leo: it seems to be like a problem in wpa_supplicant really: as you can see, when the connection succeeds you have "WPA_CLI RESULT IS COMPLETED", while you don't have that in all other cases.
I guess wpa_supplicant it's taking more time than usual to finish association.
You could try increasing the time it tries -- it's currently set to 35 seconds. Open wicd/wnettools.py, and look for MAX_TIME, and set it to, say, 60. If that solves the issue (i.e. you find a "WPA_CLI RESULT IS COMPLETED" in the log), then we need to find out why wpa_supplicant takes so long to complete (and maybe it could be a good idea letting the user set that timeout from the GUIs).
Thanks for your collaboration,
David