Could not connect to wicd's D-Bus interface. Check the wicd log for er

roastymctoasty · 2013-05-01 11:39:11

Having issues getting wireless to work on Acer V3 551. Wired works great. I'm new to Arch from Ubuntu, so please be nice to me

On startup, I get two error dialog boxes:
#1: Could not connect to wicd's D-Bus interface. Check the wicd log for error messages.
#2: The wicd daemon has shut down. The UI will not function properly until it is restarted.

Network info:
23:01:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev c0)
24:02:00.0 Network controller: Atheros Communications Inc. AR9462 Wireless Network Adapter (rev 01)

wicd-curses terminal output:
wicd-curses
Can't connect to the daemon, trying to start it automatically...
Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 1043, in <module>
setup_dbus()
File "/usr/share/wicd/curses/wicd-curses.py", line 1031, in setup_dbus
dbus_ifaces = dbusmanager.get_dbus_ifaces()
File "/usr/lib/python2.7/site-packages/wicd/dbusmanager.py", line 36, in get_dbus_ifaces
return DBUS_MANAGER.get_dbus_ifaces()
File "/usr/lib/python2.7/site-packages/wicd/dbusmanager.py", line 62, in get_dbus_ifaces
if not self._dbus_ifaces: connect_to_dbus()
File "/usr/lib/python2.7/site-packages/wicd/dbusmanager.py", line 48, in connect_to_dbus
return DBUS_MANAGER.connect_to_dbus()
File "/usr/lib/python2.7/site-packages/wicd/dbusmanager.py", line 79, in connect_to_dbus
proxy_obj = self._bus.get_object("org.wicd.daemon", '/org/wicd/daemon')
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 180, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 278, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.wicd.daemon.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.wicd.daemon.service' for details.

systemctl status dbus-org.wicd.daemon.service terminal output:
dbus-org.wicd.daemon.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)

I've tried:
- beginners install suggestions
- arch wicd suggestions
- unin/re-installing wicd
- google research to no avail

Trilby · 2013-05-01 12:09:57

Is dbus running with three processes: 2 dbus-daemon and one dbus-launch?

If not, you should be using dbus-launch in your session initialization somewhere, ~/.xinitrc is common.

roastymctoasty · 2013-05-01 12:58:15

Contents of ~/.xinitrc:

#!/bin/sh
#
#~/.xinitrc
#
# Executed by startx (run your window manager from here)

if [ -d /etc/x11/xinit/xinitrc.d; then
for f in /etc/x11/xinit/xinitrc.d/#; do
[ -x "$f" ] && . "$f"
done
unset f
fi

exec gnome-session
#exec startkde
#exec startxfce4
# ... or the window manager of your choice

Should I append something here?

Also - what best command can I issue to see if dbus is running three processes?

Last edited by roastymctoasty (2013-05-01 13:02:20)

Trilby · 2013-05-01 13:33:20

pstree, top, or htop will verify that you have not launched dbus-launch which is required for many tools including wicd.

I tend to avoid that recommended monstrosity at the top of xinitrc and I just control things myself by launching my window manager with

exec dbus-launch --exit-with-session <windowmanagername>

But that block of code at the top of your xinitrc *should* start a dbus session. It fails because there is a typo - two actually: there is no /etc/x11 folder, it is /etc/X11.

roastymctoasty · 2013-05-01 14:17:00

Two things:

Sincere apologies. I manually typed in the results of ~/.xinitrc (at work, on another computer). It does actually say /X11/xinit/... and /X11/xinit/ between the if and do - with a capital X instead of lowercase x.

I ran pstree, and I'm able to see dbus-daemon and dbus-launch in the tree.

2*[dbus-daemon]
dbus-launch

So the typos are not a problem, and I appear to have 3 dbus processes.

Any thoughts on additional steps I can take?

Also - can I replace the if / fi code block with the code you recommended in your previous post?

Last edited by roastymctoasty (2013-05-01 14:18:33)

Trilby · 2013-05-01 15:00:29

So dbus is not the issue - sorry for the misdirection. It may be a permissions issue - but I don't have any great next recommendations.

WorMzy · 2013-05-01 15:03:17

Is wicd.service enabled and running?

systemctl status wicd.service

Also, please use [ code ] tags to post output and config files.

Last edited by WorMzy (2013-05-01 15:04:17)

roastymctoasty · 2013-05-01 15:24:49

Apologies. First post to the board - will keep post within bracket tags. Sorry for being such a noob.

Input

$ systemctl status wicd.service

Output

wicd.service - Wicd a wireless and wired network manager for Linux
  Loaded: loaded (/usr/lib/systemd/system/wicd.service; disabled)
  Active: failed (Result: exit-code) since Wed 2013-05-01...
  Process: 972 ExecStart=/usr/sbin/wicd --no-daemon (code=exited, status=1/FAILURE)

Starting Wicd a wireless and wired network manager for Linux
It seems like the daemon is already running
If it is not, please remove /var/run/wicd/wicd.pid and try again.
wicd.service: main process exited, code=exited, status=1/FAILURE
Failed to start Wicd a wireless and wired network manager for linux.
MESSAGE=Unit wicd.service entered a failed state.

Any thoughts?

Last edited by roastymctoasty (2013-05-01 15:58:17)

WorMzy · 2013-05-01 16:01:18

Loaded: loaded (/usr/lib/systemd/system/wicd.service; disabled)

This shows that it is currently disabled, which means that it isn't automatically started at boot time. To fix that, you just need to enable it, using systemctl.

That status message may be problematic though, unless you've manually started wicd as root in the meantime? Could you check whether wicd is currently running?

ps aux | grep wicd

If it is, you should be able to use wicd-curses now. If not, follow the advice the status message gave you and remove the stale pid file, you should then be able to "start" the wicd.service.

roastymctoasty · 2013-05-01 17:08:41

Seems to be fixed! Thanks for helping a newbie out!

Now I just need to figure out how to connect it to my offices WPA2 Enterprise network, which may be another project entirely...

Arch Linux

#1 2013-05-01 11:39:11

Could not connect to wicd's D-Bus interface. Check the wicd log for er

#2 2013-05-01 12:09:57

Re: Could not connect to wicd's D-Bus interface. Check the wicd log for er

#3 2013-05-01 12:58:15

Re: Could not connect to wicd's D-Bus interface. Check the wicd log for er

#4 2013-05-01 13:33:20

Re: Could not connect to wicd's D-Bus interface. Check the wicd log for er

#5 2013-05-01 14:17:00

Re: Could not connect to wicd's D-Bus interface. Check the wicd log for er

#6 2013-05-01 15:00:29

Re: Could not connect to wicd's D-Bus interface. Check the wicd log for er

#7 2013-05-01 15:03:17

Re: Could not connect to wicd's D-Bus interface. Check the wicd log for er

#8 2013-05-01 15:24:49

Re: Could not connect to wicd's D-Bus interface. Check the wicd log for er

#9 2013-05-01 16:01:18

Re: Could not connect to wicd's D-Bus interface. Check the wicd log for er

#10 2013-05-01 17:08:41

Re: Could not connect to wicd's D-Bus interface. Check the wicd log for er

Board footer