wicd doesn't work

[name of]

I can't get wicd to start when I log in. wicd-gtk tells me:

Could not connect to wicd's D-Bus interface.  Check the wicd log for error messages.

i can make it start by manually typing in "wicd" on the command line as root, but it's a bit troublesome.
I've seen more than one person with this problem, but I can't seem to find any solutions. One guy says it's a selinux issue, and since selinux gripes at me every time i try to start wicd, i assume that this is a similar issue. says some nonsense about python?
here we go:

Summary:

SELinux is preventing /usr/bin/python "read" access on /var/run/wicd.pid.

Detailed Description:

SELinux denied access requested by wicd. It is not expected that this access is
required by wicd and this access may signal an intrusion attempt. It is also
possible that the specific version or configuration of the application is
causing it to require additional access.

I'd just use nm, but I'm a fan of bzflag, and nm gives me so much jitter/lag/packetloss i get kicked.
If i run wicd as root from the command line after I log in, it runs just fine. If i'm not mistaken, there should be a script in /etc/init.d that starts wicd. It definitely exists on my system, but it doesn't seem to work. 'course, if I try to put any custom init scripts in there, they don't work either, so it probably isn't the script.

[R3353]

There are guides floating around. Here's one for F11 that concludes with a nice bash script alternative to problematic GUIs.

[name of]

Originally Posted by R3353

There are guides floating around. Here's one for F11 that concludes with a nice bash script alternative to problematic GUIs.

sorry, couldn't get that to work.
Even if I did, I would be using networkmanager, and it was giving me hell.
Well, now I installed wicd from the tarball. It starts up fine, but now it gives me an error saying my password is wrong (which is totally ridiculous. The password is on the side of my modem, and I have it sitting two feet away from me).

[R3353]

I heard about this bug in wicd 1.7. There's also this, which is a guide for installing a wicd repository and proceeding in this manner.

[R3353]

I've been able to spend some time on this. Many wicd versions are available here. wicd-1.7 give the "bad password" denial when trying to connect to a WPA network. wicd-1.6.2.2 does not remember hidden networks. wicd-1.6.2.1 does both of these successfully and seems stable. One thing to note, make sure nm and wpa_supplicant are off.

As for the installation....
Using the version in the updates repo results in the "unable to connect to dbus error" even after chkconfing. Installing and using wicd's repo does not work either. Following these instructions works.

This information applies to wicd on a thinkpad T60 running F11.

[name of]

Well, post 4 seems to have worked after I restored twenty or so file contexts when SElinux made a racket; it wasn't working before. don't know why. We'll see on the next reboot, eh?
edit:
rebooted, works fine
Wicd 1.6.2.2
Fedora 13
lxde desktop environment.
pretty sure the chipset for wireless is atheros, but I've used different distros with no trouble. other than gentoo, fedora works best.
Other than a few apps and updates, everything's more or less the way it came in the lxde spin.

[R3353]

very well, glad something is up and running for you. Would you mind editing your last post to include the version of fedora, wicd, and perhaps some details regarding your setup?

Thanks,
Reese