From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dbus failures
Date: Wed, 30 Oct 2013 01:38:47 +0000 [thread overview]
Message-ID: <20131030013847.0a2f39ae@digimed.co.uk> (raw)
In-Reply-To: <87li1b6138.fsf@nyu.edu>
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
On Tue, 29 Oct 2013 20:42:35 -0400, gottlieb@nyu.edu 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.
--
Neil Bothwick
Do hungry crows have ravenous appetites?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-10-30 1:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 0:42 [gentoo-user] dbus failures gottlieb
2013-10-30 1:38 ` Neil Bothwick [this message]
2013-10-30 1:50 ` Dale
2013-10-30 1:51 ` Canek Peláez Valdés
2013-10-30 16:36 ` gottlieb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131030013847.0a2f39ae@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox