Slack 13 and wicd
 

'Ello. I cannot get wicd to work with slackware 13.

The package in extra was 16.2.1 and I'd heard that upgrading to 16.2.2 would fix it, so I removed it and got the source installed. I heard that it did not put the init files in the correct place, so I manually copied them to /etc/rc.d. I even removed /home/user/.wicd between installations like it was suggested.

However, my WPA2 encrypted ssid is still "hidden", and returns the error: "Connection failed: Could not contact the wireless access point." when I try to connect.

Also, when I use iwlist wlan0 scan, it shows the correct ssid.

Anyone, please help me. I would very much like my desktop back. This stupid dell laptop is driving me insane, help me, please, please.

Actually I suppose I could go back to 12.2 but I KNOW there's a way to get this working. >:C

Just for trying, remove the files under /var/lib/wicd. Before upgrading to 1.6.2.2, I found that doing that solved the problem for 1.6.2.1 (at least the first time starting it after clearing the files)

YMMV, but it worked for me, and as those files are autogenerated by wicd, there is nothing lost in trying. Don't remove the folders, though, as depending on the file permissions wicd may start failing apparently without reason if it is unable to create the folders again.


Regards.

Oh, thank you so much. I deleted everything that came up with whereis wicd as well as the /var/lib/wicd contents and reinstalled 1.6.2.2 (from source, mind you) and it works perfectly.

It actually *did* copy the init file correctly, so I don't think that was ever a problem.

Hmm, this still isn't working for me.

I just upgraded to 1.6.2.2 using an older slackbuild and changing the ARCH and VERSION.

I had nothing in /var/lib/wicd to delete

My router still comes up as hidden, as do a few other networks.

I am using an intel Pro/wireless 5000 card...

No idea if this is any help. CHeck out post number 11 in my thread here:
http://www.linuxquestions.org/questi...router-776443/

My problem was that both wicd and a "iwlist wlan0 scan" from the CLI were not seeing my ESSID, and post 11's fix worked for me. Guess it wouldnt hurt to try it.

mute