wicd-start does the job normally, no any other action needed. However in some cases you have to wait a bit till it starts-up, so try to run client a bit later. Are you using LXDE or Xfce4? If not, use 'wicd-client -n' to start GUI.

One more thing. Run client as user (tc) and not as root. Lets see the result.

I'm using TC 2.8.1 as a fresh install (yesterday) onto a SD card. This card is sdb1. I have all extensions installed to /mnt/sdb1/tce/optional The TC install is just your default type with nothing customised or hacked.

Yes all components are up to date. At your suggestion concering the dbus subsytem, I removed all 9 dbus files from the tce optional directory. ie dbus, dbus-python & dbus-glib (.tcz, .tcz.dep & .tcz.md5.txt variants) I replaced these extensions with older versions from Dec 2009 repository. Now wicd appears to be behaving itself!

It's getting close to midnight in this part of the world so I had best be away.

I will run the checks you suggest tomorrow and report back. Thanks for all your assistance. Much obliged.

The dbus and other extensions no longer start the service with the /usr/local/tce.installed startup script. This is being done to pave the way for recursive dependencies, and we can't have our cake and eat it too when it comes to recursion vs. controlling the order of dependency loading, which was necessary to have the startup scripts start daemons for some extensions.

The scripts in /usr/local/etc/init.d are now being used to start daemons, and those start commands can be placed in bootlocal.sh.

Hi all:I get the same error as Miller regarding the wicd-client output in both of my laptops (Acer Aspire One D150 with a Broadcomm wlan card, the wl module loaded and a Dell Inspiron 9100). I used the latest tc 2.8.1 version default install on an usb (=sdb1) with persistent tce and home. Desktop is FLWM.

I'm trying to make Tiny Core 2.8 working on a HP Mini 1110NR with Broadcom chip. I followed the instructions on the wiki, plus this post on the forum, and I've got the exact same error message except from the last part. Instead of "No such file or directory", I get a "Connexion refused" error on /var/run/dbus/system_bus_socket. I'm using wicd-client -n as normal user. Thanks.

To summarize so far, wicd appears to be running properly on a fresh (4th Feb 2010 repository) install of TC 2.8.1 only when I replace the current (dbus.tcz, dbus-glib.tcz and dbus-python.tcz) extensions (plus their respective .tcz.dep & .tcz.md5.txt files) with older versions.

The older versions I used are: dbus.tcz ver: 1.2.16 , dbus-glib.tcel ver: 0.82 , dbus-python.tcz ver: 0.83.0 NB: I have attached to this post the 3 info files (prefixed with "good-") associated with each of these older extensions I installed.

The results of the terminal "ps" show the dbus subsystem running. This output is attached as good-wicd-ps-output.txt to this post.

/*************************************************************************/As an aside, after wicd is installed I run this script to tidy up, then reboot. Thanks Bela for this.

I have attached the results of the terminal "ps" which shows the dbus subsystem not running. This output is attached as faulty-wicd-ps-output.txt to this post.

I have installed Tiny Core 2.8.1 to a MSI-Wind U100. The sata HD has been replaced with a sata-CF adapter w/2Gb flash card (sda1). I pop a 1Gb SD card in the card slot (sdb1) and install TC on it. The internal wlan is an Atheros 9280 pci-e type.