Neil Bothwick wrote: > On Tue, 29 Oct 2013 20:42:35 -0400, [email protected] wrote: > >> I am recently getting wicd failures due to inability to connect to the >> system. >> >> I get a wicd popup msg saying to look in wicd.log. However there are no >> errors listed (full log below). >> >> I do get a popup from wicd saying >> The wicd daemon has shut down. The UI will not function properly >> until it is restarted. >> >> Also (probably starting at the same time) the gui from gnome concerning >> battery power is wrong. It says 100% on the top bar (which is correct) >> but when clicked, it indicates that both batteries are at 0% > > It sounds like DBus is not running. The wicd daemon does not need DBus, > which is why your network connections still work, but the clients need > DBus to talk to the daemon. The GNME battery applet may well use DBus too? > > Is DBus actually running? Is it in any of your runlevels? > > sudo rc-update -s | grep dbus > > It runs here, even though it is not in a runlevel, because something else > depends on it. It is possible that you have either removed whatever was > pulling it in or that the init script has changed and no longer depends > on DBus. Or the dbus service is simply failing to start for some reason. > > Trying to start it from a terminal should identify which, if any, of > these is the case. > >
I would add this to see if it is running or not. ps aux | grep -i dbus Then see if dbus is listed. If it is, other than the grep command process of course, then it should be running. If not, well, Neil has some good tips to fix that. ;-) Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
