Re: [gentoo-user] dbus failures

[gottlieb@nyu.edu]

On Tue, Oct 29 2013, Neil Bothwick wrote:

> 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.

Yes dbus is in default runlevel.

It "must" have been running since I had many entries in
/var/log/messages mentioning it.  For example.

   9973:Oct 29 20:08:46 newlap dbus[2089]: [system] Activating service name='org.freedesktop.Accounts' (using servicehelper).

Canek is correct that I run gnome 3 (3.6 currently) and I am moving all
my systems to systemd (my backup laptop runs it now) so that I can run
gnome 3.8 and beyond.  However, this error occurred on my main laptop,
which still runs openRC (I will be converting it to systemd soon).

Finally and *most significantly*, last night's update world seems to
have changed the symptoms.
 * I no longer get the popup from wicd saying that it can't connect on
   the system bus 
 * The wicd ui works fine.
 * Difference in messages sent to /var/log/messages
   - Before update world.  Tries and fails twice.
   - Today.  Tries and fails; retries and succeeds (see below).

I guess I need to monitor this for a few more days.

allan

  10108:Oct 29 20:10:43 newlap dbus[2089]: [system] Activating service name='org.wicd.daemon' (using servicehelper)
  10109:Oct 29 20:10:44 newlap dbus[2089]: [system] Activated service 'org.wicd.daemon' failed: Launch helper exited with unknown return code 1
  10277:Oct 29 20:11:08 newlap dbus[2089]: [system] Activating service name='org.wicd.daemon' (using servicehelper)
  10278:Oct 29 20:11:08 newlap dbus[2089]: [system] Activated service 'org.wicd.daemon' failed: Launch helper exited with unknown return code 1

  11899:Oct 30 08:52:14 newlap dbus[2088]: [system] Activating service name='org.wicd.daemon' (using servicehelper)
  11900:Oct 30 08:52:14 newlap dbus[2088]: [system] Activated service 'org.wicd.daemon' failed: Launch helper exited with unknown return code 1
  12017:Oct 30 08:52:30 newlap dbus[2088]: [system] Activating service name='org.wicd.daemon' (using servicehelper)
  12018:Oct 30 08:52:30 newlap dbus[2088]: [system] Successfully activated service 'org.wicd.daemon'