Could not connect to wicd's D-Bus interface

[maguip22]

I have upgraded to BT5, really enjoying the new features and layout

I was running BT5 on a live CD and later installed it to the HD. When I first ran it from the CD I was exploring around the new OS and went to the network manager and connected to my router. I had full internet access and began messing around.

After a short while I tried to connect back to my router and I was getting the following errors on launching the network manager.

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

I then click my network enter the WPA passphrase and it tries to connect. I then get the error

Bad Password

------------------

Anyone know how to fix this problem? I had a look at the logs and didn't see any errors. One minute the internet is working fine the next minute I can't connect and my password is bad.

I got a little paranoid so checked my password on my other computers and could connect no problem, I am on the same laptop now - on the XP partition - and can connect fine.

I tried reboots and starting the network manually still no joy, hell even restarted the router - no joy

I then installed BT5 to my hard drive and still got the same problems.
This is really strange, I searched the internet for answers but having no joy.

-------------
DELL VOSTRO 1710
Dual boot: XP & BT5
--------------

Thanks guys

[sickness]

That error should not influence your connectivity, however this is the fix to it:

root@evilbox:~# dpkg-reconfigure wicd
root@evilbox:~# update-rc.d wicd defaults
 Adding system startup for /etc/init.d/wicd ...
   /etc/rc0.d/K20wicd -> ../init.d/wicd
   /etc/rc1.d/K20wicd -> ../init.d/wicd
   /etc/rc6.d/K20wicd -> ../init.d/wicd
   /etc/rc2.d/S20wicd -> ../init.d/wicd
   /etc/rc3.d/S20wicd -> ../init.d/wicd
   /etc/rc4.d/S20wicd -> ../init.d/wicd
   /etc/rc5.d/S20wicd -> ../init.d/wicd
root@evilbox:~#

[maguip22]

sickness thanks for the quick reply

I already tried the above code and retried it with no joy! I can't get my head around this one. Working 100% from live cd, then all of a sudden it stops, install BT5 to disk and still get the same problem.

Anything else I should try/check?

Thanks

[maguip22]

Update:

I went into 'gerix-wifi-cracker-ng' and clicked configuration and then clicked reload wireless interfaces I refreshed my Wicd network manager and tried to reconnect. This time it connected. Happy days

FAIL

After dinner booted back up BT5 and tried to connect and the 'bad password' error is coming back up.

Please help, this is so frustrating

Thanks

[2901119]

thats funny, I remeber you posting this fix in the backtrack 4 forums Sickness

[comaX]

That happens when you don't do "wicd start" before. If you still get the same error, then do as sickness says

[maguip22]

I tried that guys and it worked last night.

root@bt:~# dpkg-reconfigure wicd
root@bt:~# update-rc.d wicd defaults
 Adding system startup for /etc/init.d/wicd ...
   /etc/rc0.d/K20wicd -> ../init.d/wicd
   /etc/rc1.d/K20wicd -> ../init.d/wicd
   /etc/rc6.d/K20wicd -> ../init.d/wicd
   /etc/rc2.d/S20wicd -> ../init.d/wicd
   /etc/rc3.d/S20wicd -> ../init.d/wicd
   /etc/rc4.d/S20wicd -> ../init.d/wicd
   /etc/rc5.d/S20wicd -> ../init.d/wicd

root@evilbox:~#

was working nicely last night. I rebooted and started up later today and this happened.

root@bt:~# dpkg-reconfigure wicd
root@bt:~# update-rc.d wicd defaults
system start/stop links for /etc/init.d/wicd already exits

Do I have to do this everytime I start BT5 or can I just click on the Wicd Network Manager and conenct?

Thanks Guys

[2901119]

no you only have to do that once, after that you should no longer see the "could not connect to wicd dbus" error

[maguip22]

I don't get the could not connect to wicd dbus" error but I get the 'bad password' still.

Anymore suggestions?

whats this all about

system start/stop links for /etc/init.d/wicd already exits

[maguip22]

Booted up BT5 today when I woke up and wouldn't you know I can connect perfectly, messed around for a few hours. Had dinner then rebooted and GUESS WHAT!!! yep, BAD PASSWORD again fml

This is really annoying me right now. Can anyone please help

Thanks