wicd should detect when kernel cannot associate with AP

[Krylov Ivan]

I often get in a situation when the AP wignal is too low to get connected to it.
In this case I can see these messages in the syslog:

Dec 9 12:28:44 localhost kernel: wlan0: direct probe to <BSSID> (try 1/3)
Dec 9 12:28:44 localhost kernel: wlan0: direct probe to <BSSID> (try 2/3)
Dec 9 12:28:44 localhost kernel: wlan0: direct probe to <BSSID> (try 3/3)
Dec 9 12:28:45 localhost kernel: wlan0: direct probe to <BSSID> timed out

But WICD ignores this and tries to obtain an IP-address anyway:
Dec 9 12:28:46 localhost dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
Dec 9 12:28:46 localhost dhclient: Copyright 2004-2010 Internet Systems Consortium.
Dec 9 12:28:46 localhost dhclient: All rights reserved.
Dec 9 12:28:46 localhost dhclient: For info, please visit https://www.isc.org/software/dhcp/
Dec 9 12:28:46 localhost dhclient:
Dec 9 12:28:46 localhost dhclient: Listening on LPF/wlan0/70:f1:a1:ba:6a:a1
Dec 9 12:28:46 localhost dhclient: Sending on LPF/wlan0/70:f1:a1:ba:6a:a1
Dec 9 12:28:46 localhost dhclient: Sending on Socket/fallback
Dec 9 12:28:50 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6

So I have to manually view logs while connecting and stop trying to connect if I see this.

I think that it would be more comfortable if WICD detects it automatically.

For example the "iw" utility has the command:
 dev <devname> connect [-w] <SSID> [<freq in MHz>] [<bssid>] [key 0:abcde d:1:6162636465]
                Join the network with the given SSID (and frequency, BSSID).
                With -w, wait for the connect to finish or fail.

But it cannot be used because its output is not considered stable by its developers.

I am using Wicd 1.7.0 from Debian wheezy.