SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Today when I turn on my laptop I get this error initialize wicd:
Quote:
bash-3.1# wicd
bash-3.1# wicd-client
libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Could not initalize pynotify
Has notifications support False
Loading...
Connecting to daemon...
Can't connect to the daemon, trying to start it automatically...
Wicd daemon is shutting down!
The last program I installed was xfce4-power-manager 0.8.3.1 form a slackbuild that I made.
I uninstall xfce4-power-manager and the error continuous, what can I do?
Thank for the reply, but I tried that and I have the same problem.
I remember something, I accidentally remove /tmp/ folder, I make sudo mkdir /tmp/, is this relevant?
When I try to run wicd-curses I get this error:
Quote:
bash-3.1# wicd-curses
Can't connect to the daemon, trying to start it automatically...
Traceback (most recent call last):
File "/usr/lib64/wicd/wicd-curses.py", line 1034, in <module>
setup_dbus()
File "/usr/lib64/wicd/wicd-curses.py", line 1024, in setup_dbus
dbus_ifaces = dbusmanager.get_dbus_ifaces()
File "/usr/lib64/python2.6/site-packages/wicd/dbusmanager.py", line 36, in get_dbus_ifaces
return DBUS_MANAGER.get_dbus_ifaces()
File "/usr/lib64/python2.6/site-packages/wicd/dbusmanager.py", line 62, in get_dbus_ifaces
if not self._dbus_ifaces: connect_to_dbus()
File "/usr/lib64/python2.6/site-packages/wicd/dbusmanager.py", line 48, in connect_to_dbus
return DBUS_MANAGER.connect_to_dbus()
File "/usr/lib64/python2.6/site-packages/wicd/dbusmanager.py", line 79, in connect_to_dbus
proxy_obj = self._bus.get_object("org.wicd.daemon", '/org/wicd/daemon')
File "/usr/lib64/python2.6/site-packages/dbus/bus.py", line 244, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib64/python2.6/site-packages/dbus/proxies.py", line 241, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib64/python2.6/site-packages/dbus/bus.py", line 183, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib64/python2.6/site-packages/dbus/bus.py", line 281, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib64/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
Can anyone help me?
Last edited by mlpa; 10-10-2009 at 05:25 AM.
Reason: New error
Instead of editing to qualify a post for information you should either note the change or append the information. Sometimes history information can be used to aid with the new error information.
If you re-create the '/tmp' as root and you re-boot. Do you still see the error? What about checking processes with 'ps -aux'?
When you re-create a missing /tmp, you should also give it proper attributes. Every user has to be able to write in /tmp or a lot of processes will simply not work correctly. As root:
I solved the problem, when I run wicd -foe, I get a parser error, for the file /etc/wicd/wired-settings.conf, because the extra '\n' just remove the final change of line in that file and restart the deamon.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.