Tiny Core Linux
Tiny Core Extensions => TCE Bugs => Topic started by: jur on February 24, 2010, 02:08:16 AM
-
tc@box:~$ wicd-client
/usr/local/bin/wicd-client: line 2: tput: command not found
/usr/local/bin/wicd-client: line 3: tput: command not found
/usr/local/bin/wicd-client: line 4: tput: command not found
Traceback (most recent call last):
File "/usr/local/share/wicd/gtk/wicd-client.py", line 63, in <module>
from wicd import dbusmanager
File "/usr/local/lib/python2.6/site-packages/wicd/dbusmanager.py", line 93, in <module>
DBUS_MANAGER = DBusManager()
File "/usr/local/lib/python2.6/site-packages/wicd/dbusmanager.py", line 57, in __init__
self._bus = dbus.SystemBus()
File "/usr/local/lib/python2.6/site-packages/dbus/_dbus.py", line 202, in __new__
private=private)
File "/usr/local/lib/python2.6/site-packages/dbus/_dbus.py", line 108, in __new__
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
File "/usr/local/lib/python2.6/site-packages/dbus/bus.py", line 125, in __new__
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBu.ception: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
I need help, please...
-
Looks like DBUS daemon is not running at first glance.
Are you starting WICD according to the info file with command 'sudo wicd-start' ?
-
Yes. I just started getting the dbus messages after last night's update.
I'll delete dbus and download it again.
-
Make sure that all of the extensions are up to date.
-
OK that didn't help...
As far as I know, they are all up to date as last night I used tce-update which does all it finds in batch mode.
Looks like I may have to delete absolutely everything and start from scratch to make sure there isn't something that was skipped for whatever reason.
Is there some way dbus should be started?
-
Is there some way dbus should be started?
Yes:
$ sudo /usr/local/etc/init.d/dbus [start|stop|restart|status]
but it is done by WICD.
Advice is to make a clean install on USB stick and try it.
-
OK I'll report back when I have done that. It may take a day or so.
-
Previous version of pygobject.tcz was restored in the repository rolling back faulty update made on February 23. Tested, WICD now works again.
-
Right, pygobject did not fix my problem so I started fresh and now it's OK again.