Wicd-gtk connects to the wrong AP

[a]

Arch Linux x86 (rolling release, up to date)
wicd-gtk 1.7.2.4-9
When two or more APs with the same ESSID are present, clicking "Connect" for one might connect to the other instead. This happens whether the channel is the same or not. It doesn't matter whether "Never connect to this network" is checked for the AP wicd chooses to connect to.

`iwlist scan` output, cropped to show only the two APs with the same ESSID (I was trying to connect to "Cell 02", but wicd chose "Cell 01" instead) :
          Cell 01 - Address: 00:18:F8:26:D7:AB
                    ESSID:"linksys"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.412 GHz (Channel 1)
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Signal level=100/100
          Cell 02 - Address: 00:1E:E5:3D:B9:09
                    ESSID:"linksys"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.417 GHz (Channel 2)
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    IE: Unknown: DD720050F204104A0001101044000101103B00010310470010001EE53DB907001EE53DB9070400E8001021000C4C696E6B73797320496E632E102300075752543136304E1024000876312E30312E3232104200033030301054000800060050F2040001101100075752543136304E100800020088
                    Signal level=100/100

[John Boiles (johnaboiles)]

I bet this is caused by https://bugs.launchpad.net/wicd/+bug/1086573

In short, the templates for wpa supplicant need to have a line specifying BSSID. It's possible to manually add it by editing the template (in /etc/wicd/encryption/templates/on my Raspberry PI) and adding the line

bssid=$_BSSID

Doesn't fix the issue where the wrong AP is shown as connected, but you can verify the proper one is connected by running iwconfig