-   Linux - Networking (
-   -   Why is it that wicd has issues connecting to new AP's after sleeping? (

chrisportela 07-06-2011 10:28 PM

Why is it that wicd has issues connecting to new AP's after sleeping?
I was using wicd on a spotty network, the house blocked a lot of the signal from moving around, so wicd was having major issues with that AP. Later I was trying to connect to another AP but wicd couldn't connect plus it was saying the spotty network's name was the one it was connecting to. Although I didn't try before I left/gave up I'm sure a restart of the wicd daemon would have solved it.

But why is this even the case? is there something I could add to the scripts that would clear this issue up?

(I also submitted a bug on wicd's launchpad project but haven't gotten any response... I hope this isn't a 'feature')

markush 07-07-2011 01:44 PM

Hello chrisportela,

my experience with wicd is, the only reasonable action for this program is to uninstall it.

You should try wpa_supplicant without wicd, this is the most reliable setup in most cases.


chrisportela 07-08-2011 08:48 AM

Well I was unable to connect to my network using wpa_supplicant. I couldn't get the config files to work correctly unless I used some 'quick connect' utility which I don't think I have installed on this machine anymore after I re-installed arch.

Where could I go to figure it out but it actually works because the arch wiki didn't help. Or at least they were missing something.

markush 07-08-2011 09:10 AM

Could you please provide more information about your network (which encryption) and you hardware, which NIC? please post the output of

lspci -k | grep -iA5 wire


All times are GMT -5. The time now is 11:08 PM.