I posted a solution to this problem from the beginning
Code:dpkg-reconfigure wicd update-rc.d wicd defaults
Some other forum members and myself have had "Could not connect to wicd's D-Bus interface." pop up when starting X. The log, however, shows no errors. Enabling network start on boot solves the issue, but can be annoying to some of us. I've found a simple workaround that removes the error without starting the network at boot.
Move wicd-tray.desktop out of etc/xdg/autostart and place it somewhere else if needed later. Now when starting up, the error will be gone, but will pop up again if you start wicd-client or wicd-gtk. To prevent this, networking has to be enabled first.
To start networking and the wicd gtk interface in one click, you can right click on the Services>NETWORK>"WICD gtk interface" selection and select "edit item". Then change the command to:
Now the error's gone, networking doesn't start at boot, and wicd is enabled with one clickCode:sh -c "start-network && wicd-gtk"![]()
I posted a solution to this problem from the beginning
Code:dpkg-reconfigure wicd update-rc.d wicd defaults
Back|track giving machine guns to monkeys since 2007 !
Do not read the Wiki, most your questions will not be answered there !
Do not take a look at the: Forum Rules !
Yes, and I tried your fix, but it started network at boot. I'd rather not do that if I can avoid it.
Here are 2 ideas, 1 go search the forums. It's a rule you agreed to uphold and follow. So now is a good time to start.
Second, if you don't know what commands you are running then it might be good to look into them. I mean how to do know the guy didn't just post a command to delete your hard drive(s).
If these two tasks are to much for you then go back to whatever operating system you came from. We are not here to teach you how to use linux.
To be successful here you should read all of the following.
ForumRules
ForumFAQ
If you are new to Back|Track
Back|Track Wiki
Failure to do so will probably get your threads deleted or worse.