| 1 |
On Tue, Oct 29 2013, Neil Bothwick wrote: |
| 2 |
|
| 3 |
> On Tue, 29 Oct 2013 20:42:35 -0400, gottlieb@×××.edu wrote: |
| 4 |
> |
| 5 |
>> I am recently getting wicd failures due to inability to connect to the |
| 6 |
>> system. |
| 7 |
>> |
| 8 |
>> I get a wicd popup msg saying to look in wicd.log. However there are no |
| 9 |
>> errors listed (full log below). |
| 10 |
>> |
| 11 |
>> I do get a popup from wicd saying |
| 12 |
>> The wicd daemon has shut down. The UI will not function properly |
| 13 |
>> until it is restarted. |
| 14 |
>> |
| 15 |
>> Also (probably starting at the same time) the gui from gnome concerning |
| 16 |
>> battery power is wrong. It says 100% on the top bar (which is correct) |
| 17 |
>> but when clicked, it indicates that both batteries are at 0% |
| 18 |
> |
| 19 |
> It sounds like DBus is not running. The wicd daemon does not need DBus, |
| 20 |
> which is why your network connections still work, but the clients need |
| 21 |
> DBus to talk to the daemon. The GNME battery applet may well use DBus too? |
| 22 |
> |
| 23 |
> Is DBus actually running? Is it in any of your runlevels? |
| 24 |
> |
| 25 |
> sudo rc-update -s | grep dbus |
| 26 |
> |
| 27 |
> It runs here, even though it is not in a runlevel, because something else |
| 28 |
> depends on it. It is possible that you have either removed whatever was |
| 29 |
> pulling it in or that the init script has changed and no longer depends |
| 30 |
> on DBus. Or the dbus service is simply failing to start for some reason. |
| 31 |
> |
| 32 |
> Trying to start it from a terminal should identify which, if any, of |
| 33 |
> these is the case. |
| 34 |
|
| 35 |
Yes dbus is in default runlevel. |
| 36 |
|
| 37 |
It "must" have been running since I had many entries in |
| 38 |
/var/log/messages mentioning it. For example. |
| 39 |
|
| 40 |
9973:Oct 29 20:08:46 newlap dbus[2089]: [system] Activating service name='org.freedesktop.Accounts' (using servicehelper). |
| 41 |
|
| 42 |
Canek is correct that I run gnome 3 (3.6 currently) and I am moving all |
| 43 |
my systems to systemd (my backup laptop runs it now) so that I can run |
| 44 |
gnome 3.8 and beyond. However, this error occurred on my main laptop, |
| 45 |
which still runs openRC (I will be converting it to systemd soon). |
| 46 |
|
| 47 |
Finally and *most significantly*, last night's update world seems to |
| 48 |
have changed the symptoms. |
| 49 |
* I no longer get the popup from wicd saying that it can't connect on |
| 50 |
the system bus |
| 51 |
* The wicd ui works fine. |
| 52 |
* Difference in messages sent to /var/log/messages |
| 53 |
- Before update world. Tries and fails twice. |
| 54 |
- Today. Tries and fails; retries and succeeds (see below). |
| 55 |
|
| 56 |
I guess I need to monitor this for a few more days. |
| 57 |
|
| 58 |
allan |
| 59 |
|
| 60 |
10108:Oct 29 20:10:43 newlap dbus[2089]: [system] Activating service name='org.wicd.daemon' (using servicehelper) |
| 61 |
10109:Oct 29 20:10:44 newlap dbus[2089]: [system] Activated service 'org.wicd.daemon' failed: Launch helper exited with unknown return code 1 |
| 62 |
10277:Oct 29 20:11:08 newlap dbus[2089]: [system] Activating service name='org.wicd.daemon' (using servicehelper) |
| 63 |
10278:Oct 29 20:11:08 newlap dbus[2089]: [system] Activated service 'org.wicd.daemon' failed: Launch helper exited with unknown return code 1 |
| 64 |
|
| 65 |
11899:Oct 30 08:52:14 newlap dbus[2088]: [system] Activating service name='org.wicd.daemon' (using servicehelper) |
| 66 |
11900:Oct 30 08:52:14 newlap dbus[2088]: [system] Activated service 'org.wicd.daemon' failed: Launch helper exited with unknown return code 1 |
| 67 |
12017:Oct 30 08:52:30 newlap dbus[2088]: [system] Activating service name='org.wicd.daemon' (using servicehelper) |
| 68 |
12018:Oct 30 08:52:30 newlap dbus[2088]: [system] Successfully activated service 'org.wicd.daemon' |
Archives