| 1 |
On Tue, 29 Oct 2013 20:42:35 -0400, gottlieb@×××.edu wrote: |
| 2 |
|
| 3 |
> I am recently getting wicd failures due to inability to connect to the |
| 4 |
> system. |
| 5 |
> |
| 6 |
> I get a wicd popup msg saying to look in wicd.log. However there are no |
| 7 |
> errors listed (full log below). |
| 8 |
> |
| 9 |
> I do get a popup from wicd saying |
| 10 |
> The wicd daemon has shut down. The UI will not function properly |
| 11 |
> until it is restarted. |
| 12 |
> |
| 13 |
> Also (probably starting at the same time) the gui from gnome concerning |
| 14 |
> battery power is wrong. It says 100% on the top bar (which is correct) |
| 15 |
> but when clicked, it indicates that both batteries are at 0% |
| 16 |
|
| 17 |
It sounds like DBus is not running. The wicd daemon does not need DBus, |
| 18 |
which is why your network connections still work, but the clients need |
| 19 |
DBus to talk to the daemon. The GNME battery applet may well use DBus too? |
| 20 |
|
| 21 |
Is DBus actually running? Is it in any of your runlevels? |
| 22 |
|
| 23 |
sudo rc-update -s | grep dbus |
| 24 |
|
| 25 |
It runs here, even though it is not in a runlevel, because something else |
| 26 |
depends on it. It is possible that you have either removed whatever was |
| 27 |
pulling it in or that the init script has changed and no longer depends |
| 28 |
on DBus. Or the dbus service is simply failing to start for some reason. |
| 29 |
|
| 30 |
Trying to start it from a terminal should identify which, if any, of |
| 31 |
these is the case. |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
Neil Bothwick |
| 36 |
|
| 37 |
Do hungry crows have ravenous appetites? |
Archives