The solution posted by BrZ works! When I upgraded wicd from 1.6.6.1 to 1.6.6.2 the problem remained. It solved the "ESSID with spaces" problem (I could see other previously "hidden" networks, but mine was still "hidden"). Then, I removed the package and any traces of wicd, even the ones in $HOME/.wicd and reinstalled 1.6.6.2 and everything is working fine since then...

sairum++

I guess relevant wicd "traces" which should be removed after removepkg are $HOME/.wicd and /etc/wicd. At least, that worked for me.

Great!! It worked for me as well. Thanks everyone for the help. Hope PV gets this into the updates soon so others won't be affected.

Dan

I just got around to installing Slackware 13_x86 (32 bit), and I'm having this same problem -- I can't connect to an encrypted network.

Is an updated package available, or do I need to download the source and edit the Slackbuild to make a new package?

EDIT: I just checked Slackware.com and I don't see a new version in the changelog.

Robby, Pat, Eric, are you guys aware of this problem?

Regards,

As noted in at least one other thread, I've been having this "hidden network" problem as well since upgrading to 13.0.

Couldn't help but notice this at the beginning of the -current changelog, right under the announcement of 13.0:

"extra/wicd/wicd-1.6.2.1-i486-1.txz: Upgraded.
Thanks to Adam Blackburn of the Wicd team working with us on this,
and to macavity for testing the hidden network changes."

... so, something happened there ...

GB

Thanks,

Maybe I need to grab the package from -current. It would be nice if it became a patch for -stable.

I'll try it this evening and see if it works.

Regards,

Same problem here, I can't connect to an encrypted network with 13.0 using either wicd-1.6.2.1 or wicd-1.6.2.2. The encryption method is hex WEP.

I also tried downgrading to wicd-1.5.6 which worked well for me in 12.2. That didn't work because wicd-client wouldn't start under Slack 13.0, something about python errors.

Yeah, I upgraded to the version of Wicd from --current and it didn't work any better.

Oh well. I'll keep chipping away at the problem.

If I bring up the wireless interface with command line tools it works fine. (Note: I'm using a static IP on my LAN with specified nameservers):

I had wicd working perfectly in Slack 12.2. Can't get it to work with WEP in 13.0. It could be operator error though, I'm still checking.

I've temporarily given up on Wicd and reinstalled my WPA_Supplicant.conf, rc.inet1.conf, and rc.wireless.conf files from my previous installation. They work fine.

Hi,

I've been working on my Dell for a little while now. 'wicd 1.6.2.1' stopped working completely. I removed the config files and then tried too re-config. No luck.

I then decided too upgrade to 'wicd 1.6.2.2'. Backup my configuration files then I 'removepkg wicd-1.6.2.1'. I then noticed that 4 files would remain because tagged as new/updated. You may/will get a list of warnings when you 'removepkg'. These files were removed manually. I then removed the '/home/user/.wicd' directory completely.

I then used the wicd.SlackBuild by modifying the Version number to 1.6.2.2 then moved wicd-1.6.2.2.tar.bz2 to my working directory. Then just execute 'wicd.SlackBuild', after which you will need to installpkg. After the package is installed I then copied the configure files to '/etc/wicd'. I did a shutdown since I had modified the BIOS. I restored the BIOS to the correct state then re-boot Slackware 13/x86_64 to find the wireless working.

All my APs were listed and accessible.

Lufbery & onebuck,

As discussed by the OP, wicd-1.6.2.1 incorrectly reports some networks as <hidden>. Upgrading to wicd-1.6.2.2 using the procedure described by onebuck fixes the <hidden> problem for me, but as Lufbery & I are seeing it still doesn't connect using encryption (I'm using hex WEP).

I removepkg'd wicd-1.6.2.2 and downgraded to an older version, wicd-1.5.9. I had to copy the wicd directory from /usr/lib/python2.5/site-packages/ to /usr/lib/python2.6/site-packages/ to get it to work under Slack 13.0. I can't recommend that anyone else do that because I'm not sure what kind of side effects it might have. But the older version of wicd worked for me like it did in Slackware 12.2.

David,

Thanks for the heads-up. I can give that a try. Would a symlink from /usr/lib/python2.5/site-packages/ to /usr/lib/python2.6/site-packages/ work? I may give that a try.

Regards,

or you could just use the SlackBuild to build a proper package for you SW version with the newest version of wicd

Shadowsnipes, the point seems to be that the newest version doesn't connect to WEP-protected networks for some of us. I downloaded and ran the version in -current to no effect.