Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 05-24-2011, 07:39 PM   #1
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Rep: Reputation: 105Reputation: 105
downgrading wicd

I just upgraded to 13.37, and for some reason wicd now cannot connect to my wireless point. It keeps saying the password is wrong, when I know for an absolute fact that it is correct (even changed the password to '1' just to make sure, and no dice. Which is weird because even though its the exact same version of wicd, and not only that, it no longer seems to be able to see networks with my built in card, so having to use a USB card.

Anyway, googling turned up very little. Seems to be a common problem across distros, and some people reported that downgrading to 1.6.x fixes it. So, I ran
removepkg wicd
, and it uninstalled wicd. Downloaded wicd- from a 13.0 mirror and did
installpkg wicd-
while in the correct directory. It installed, and I ran wicd. But checking the version number when it loaded, it says its 1.7.0 again.

Not really sure why this happens. I'm assuming there's some remnant of wicd that removepkg doesn't dump, and its preventing me from installing this older version of wicd. What do I need to do for this?

Or if anyone has a surefire way to make 1.7 work again, that would be fine too.
Old 05-24-2011, 09:42 PM   #2
LQ Guru
Registered: Sep 2003
Location: Danville, VA
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296

Rep: Reputation: 168Reputation: 168
Hi Cultist, Welcome to LQ. Are you certain that wicd is the problem? Can you see any ap's with wireless tools?

# iwlist ethX scan
# iwconfig
Where ethX is your interface. There may be an underlying cause.

Good luck. ;-)
Old 05-24-2011, 10:24 PM   #3
Registered: Apr 2011
Posts: 32

Rep: Reputation: 3
I am not sure what is wrong with your wicd, but at my friend's house I have to tell wicd that the WEP password is in hex when it actually isn't.
Old 05-25-2011, 12:45 AM   #4
Registered: Jan 2010
Distribution: Slackware 13.37
Posts: 598
Blog Entries: 3

Rep: Reputation: 190Reputation: 190
May not be the best solution for you but I hear rworkmans 'network manager' packages work very well..
Old 05-25-2011, 02:59 AM   #5
Mark Pettit
Registered: Dec 2008
Location: Cape Town, South Africa
Distribution: Slackware 14.2 64 Multi-Lib
Posts: 523

Rep: Reputation: 210Reputation: 210Reputation: 210
I agree with @D1ver - maybe this is the time to move to NetworkManager. I just did and I've had no problems.
Old 05-25-2011, 06:51 AM   #6
Registered: Oct 2010
Location: Pittsburgh, PA
Distribution: Slackware
Posts: 270

Rep: Reputation: 87
I kinda went the other way on Network Manager... just too much gnome crap, and yet another "key ring" to install, but I think wicd was hosing me up.

I ended up removing wicd and am now just using wpa_gui (included in slackware stock) and am rapidly forgetting why I ever installed wicd in the first place.

If you are just wanting to use a program to hook into wifi, check it out. It's pretty simple and can update your wpa_supplicant.conf directly (once you put the line update_config=1 in the file.
Old 05-25-2011, 10:03 AM   #7
Registered: Apr 2011
Posts: 32

Rep: Reputation: 3
Interesting. I had no idea that wpa_gui existed. I just ran it now, and it looks promising, except for the fact that I couldn't interact with it. Everything was greyed out.

Do you need to be root to use wpa_gui? Or do I need to uninstall or shutdown wicd?

What about wep and unsecured access points? Can wpa_gui handle those? (If not, it's not that big of a deal as going to CLI route for wep and unsecured access points in simple.)
Old 05-25-2011, 11:45 AM   #8
Registered: Oct 2010
Location: Pittsburgh, PA
Distribution: Slackware
Posts: 270

Rep: Reputation: 87
wep and unsecured should be no issue. I just went through hell with wicd issues. Check my post out here:
for some details. To interact, you need to run it kdesu wpa_gui (or equivelent) or do my alternate method from that post. You should be able to see some of it, even with wicd... but I wouldn't do anything until you have wicd off your system and dead.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
WICD tray icon says not connected, WICD manager says conneted to wired network?!?! intheshadows Linux - Newbie 1 12-24-2009 12:15 PM
Downgrading from Debian 4.0 Acoole Linux - Server 1 06-08-2007 06:56 AM
Downgrading to X86 v3 Maxicat Linux - Software 6 10-10-2004 01:45 PM
Downgrading from 3.3 to 3.2 Niumex Linux - Distributions 0 09-02-2004 04:00 PM
Downgrading MamaDoll Linux - General 1 04-11-2003 04:17 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:00 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration