You are not logged in.
Pages: 1
[user@myhost ~]$ wicd-client
Traceback (most recent call last):
File "/usr/lib/wicd/wicd-client.py", line 50, in <module>
import wicd.gui as gui
File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 2006, in <module>
setup_dbus()
File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 174, in setup_dbus
proxy_obj = bus.get_object("org.wicd.daemon", '/org/wicd/daemon')
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 244, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 241, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 183, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 281, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.wicd.daemon was not provided by any .service files
Having problems starting wicd...:(
I need some help, thanks in advance
Netbook (Acer Aspire One 110 || 160gb SATA HD || 1.5gb ram): archlinux i686 / KDEmod 4.3
Registered Linux User # 481212 / Machine Registration # 390468
"In a world without walls and fences, who needs windows and gates?"
Offline
Any ideas?
Netbook (Acer Aspire One 110 || 160gb SATA HD || 1.5gb ram): archlinux i686 / KDEmod 4.3
Registered Linux User # 481212 / Machine Registration # 390468
"In a world without walls and fences, who needs windows and gates?"
Offline
I was having the same problem... I don't know what is causing the problem and I couldn't get it to work, so I uninstalled wicd and installed wicd-svn from the AUR which now works fine. Hope this helps.
Offline
Last night I've installed Arch on the eee pc with XFCE4 as it's de, installing wicd was flawless...:D
I don't know why this happend on my KDEmod on eee pc...
Netbook (Acer Aspire One 110 || 160gb SATA HD || 1.5gb ram): archlinux i686 / KDEmod 4.3
Registered Linux User # 481212 / Machine Registration # 390468
"In a world without walls and fences, who needs windows and gates?"
Offline
Before the recent update I solved this problem by re-installing dbus-core
Not any more...
Offline
I rolled back from wicd 1.5.5 to 1.5.4 and WICD works again.
8-) Arch Linux updates are like wine spilt on new table-cloth - happen suddenly and break something
Offline
I guess you're right, the problem is with wicd...On my XFCE4 I'm using wicd 1.5.3..:D
Netbook (Acer Aspire One 110 || 160gb SATA HD || 1.5gb ram): archlinux i686 / KDEmod 4.3
Registered Linux User # 481212 / Machine Registration # 390468
"In a world without walls and fences, who needs windows and gates?"
Offline
I rolled back from wicd 1.5.5 to 1.5.4 and WICD works again.
8-) Arch Linux updates are like wine spilt on new table-cloth - happen suddenly and break something
Some updates are really not that smooth,but well, the package was not mine, i had to have my fair share of errors upgrading it. And all because I like to keep packages, even though they are not mine, up to date.
Well, here is the solution for some of the problems with the latest update:
Success! Gullible Jones' suggestion worked perfectly.
For those interested, here are the original permissions of /var/log/wicd after a fresh install:
drwxr-xr-x 2 root root 6 2008-12-02 18:16 wicdI stopped wicd, removed the directory, and restarted wicd. It was recreated like this:
d-wxrw--wt 2 root root 21 2008-12-04 19:15 wicdSo, an easy solution would probably be to have the installer package initially create the directory with these permissions. Or, conversely, _don't_ create the directory and let wicd do it on initial start.
Anyway, I'm good now. Thanks a bunch for the suggestion.
Enjoy!
Last edited by kensai (2008-12-05 02:20:25)
Offline
Oh, no, no criticism (which is plain unfair).
I consider Arch experience fun. Only two months on it and I already firmly believe that distro-hopping is over for me.
If things break, we fix them or look for solutions. Thank you for your hard work!!!
Offline
Is this still valid in wicd 1.5.9?
Offline
What I meant was, do we still have to maintain these permissions in wicd 1.5.9? Or let the /var/log/wicd directory have the standard 755 permissions?
Offline
Pages: 1