I've had slack setup for a couple months now, and after a few abortive attempts to manually get my network setup using wpa_supplicant, I decided, partially due to the frequency with which I use a wide variety of networks, that it would just be easier to let a pre-built program do the trick, and so I downloaded and installed Wicd, which has been working fine.
However, during those abortive attempts I did something which has caused for an extremely time-consuming and annoying error message, the aforementioned Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory, to occur on startup. And when I say occur, I mean occur. It is repeated probably around thirty times with a period of about one second, and that is one annoying half of a minute that I don't want to have to deal with. I should note by the way that it is preceded by a series of error messages, usually "failed to parse..." before just about every line in the wpa_supplicant. I currently have the wpa_supplicant blank:
# This line enables the use of wpa_cli which is used by rc.wireless
# if possible (to check for successful association)
# By default, only root (group 0) may use wpa_cli
# WPA protected network, supply your own ESSID and WPAPSK here:
#group=CCMP TKIP WEP104 WEP40
#psk below was made with wpa_passphrase
But have tried to fill it out to the setup for my primary network, which didn't work whatsoever. In addition, wpa_ctrl_open, which I think is supposed to be set by default to /var/run/wpa_supplicant (basing that on looking around trying to solve this on my own), has a single file named wlan0 in it, which is completely blank.
It isn't the most pressing issue because it's more of an annoyance than anything, but if somebody has had this issue before and would be willing to help me solve it, I'd be very thankful. I'm more than willing to post the contents of any other files if need be.