WICD "Could not connect to wicd's D-bus interface"

Psyconaughty · 2012-07-09 03:04:43

I'm getting this error when using WICD.

Could not connect to wicd's D-bus interface. Check the wicd log for error message.

When I run wicd-client thru the terminal I get:

[scott@Arch ~]$ wicd-client

** (process:1372): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

** (process:1372): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'

** (process:1372): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
Has notifications support True
Loading...
Connecting to daemon...
Can't connect to the daemon, trying to start it automatically...
Can't connect to the daemon, trying to start it automatically...
Failed to find a graphical sudo program, cannot continue.

I tried to find the wicd config files in /etc/wicd but could not find them. I also cannot seem the find the log file that the error message is telling me to look at.

I have installed:

wicd 1.7.2.4-3
wicd-gtk 1.7.2.4-3
dbus-core 1.6.2-2
dbus 1.6.2-1
slim 1.3.3-5
xfce 4.10
xfce4-goodies

Inxsible · 2012-07-09 04:07:28

have you started the wicd daemon? show us your DAEMONS array

Psyconaughty · 2012-07-09 04:22:36

rc.conf :

DAEMONS=(ntpd syslog-ng dbus wicd netfs crond)

Also, if i use wicd-curse I get:

[scott@Arch ~]$ 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.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1

Inxsible · 2012-07-09 05:05:31

first off I would move the ntpd after wicd. daemons that require the network should be started after the network is up

JackH79 · 2012-07-09 08:46:56

Maybe the wiki can help.

Edit: There's also this thread. Might be a similar issue.

Last edited by JackH79 (2012-07-09 08:52:06)

Psyconaughty · 2012-07-09 16:39:19

JackH79 wrote:

Maybe the wiki can help.
Edit: There's also this thread. Might be a similar issue.

I've looked at the wiki.
-I don't think I need ck-launch-session because I have slim, plus I've tried it and it didn't work.
-I've done a complete reinstall a few times with no success.
-And there seem to be no config files in the folder /etc/wicd.
I've also looked at the other thread, and I have all the necessary Xorg stuff.

venam · 2012-07-09 19:15:52

Hello Psyconaughty,
I remember having the exact similar issue on another distro, however it did not interfere with the connection (I could still connect to the internet correctly).
What I've done to solve this problem on the other distro is the following:
dpkg-reconfigure wicd
update-rc.d wicd defaults
I am not sure about the commands here, maybe they are not valid for Arch.
hope this help.

Psyconaughty · 2012-07-09 21:31:19

venam wrote:

Hello Psyconaughty,
I remember having the exact similar issue on another distro, however it did not interfere with the connection (I could still connect to the internet correctly).
What I've done to solve this problem on the other distro is the following:
dpkg-reconfigure wicd
update-rc.d wicd defaults
I am not sure about the commands here, maybe they are not valid for Arch.
hope this help.

I tried this earlier and Arch doesn't recognise the commands. I think that is a Debian command(Correct me if I'm wrong). I also assume that uninstalling it a reinstalling it would do the rconfigure but it it dosen't someone let me know how to auto reconfigure.

Also I went into my daemon log and saw some falures. The problem looks like it might be ConsoleKit. I have reinstalled ConsoleKit and still getting errors.

Here is my last loggin (From file /var/log/daemon.log):

#########
Jul  9 15:58:05 localhost init: Switching to runlevel: 6
Jul  9 15:58:06 localhost dhcpcd[1416]: received SIGTERM, stopping
Jul  9 15:58:06 localhost dhcpcd[1416]: eth0: removing interface
Jul  9 11:59:28 localhost [    1.773006] udevd[82]: starting version 185
Jul  9 11:59:28 localhost [    4.346105] udevd[198]: starting version 185
Jul  9 11:59:30 localhost ntpd[520]: ntpd 4.2.6p5@1.2349-o Sat Jun  9 05:23:54 UTC 2012 (1)
Jul  9 11:59:30 localhost ntpd[521]: proto: precision = 0.248 usec
Jul  9 11:59:30 localhost ntpd[521]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Jul  9 11:59:30 localhost ntpd[521]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Jul  9 11:59:30 localhost ntpd[521]: Listen and drop on 1 v6wildcard :: UDP 123
Jul  9 11:59:30 localhost ntpd[521]: Listen normally on 2 lo 127.0.0.1 UDP 123
Jul  9 11:59:30 localhost ntpd[521]: Listen normally on 3 lo ::1 UDP 123
Jul  9 11:59:30 localhost ntpd[521]: peers refreshed
Jul  9 11:59:30 localhost ntpd[521]: Listening on routing socket on fd #20 for interface updates
Jul  9 11:59:38 localhost dbus[471]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Jul  9 11:59:39 localhost console-kit-daemon[597]: WARNING: polkit_authority_get: Error getting authority: Error initializing authority: Could not connect: No such file or directory
Jul  9 11:59:39 localhost dbus[471]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Jul  9 11:59:44 localhost dbus[471]: [system] Activating service name='org.wicd.daemon' (using servicehelper)
Jul  9 11:59:44 localhost dbus[471]: [system] Activated service 'org.wicd.daemon' failed: Launch helper exited with unknown return code 1
Jul  9 11:59:44 localhost console-kit-daemon[597]: CRITICAL: polkit_authority_check_authorization: assertion `POLKIT_IS_AUTHORITY (authority)' failed
Jul  9 11:59:44 localhost dbus[471]: [system] Activating service name='org.wicd.daemon' (using servicehelper)
Jul  9 11:59:44 localhost dbus[471]: [system] Activated service 'org.wicd.daemon' failed: Launch helper exited with unknown return code 1
Jul  9 11:59:45 localhost console-kit-daemon[597]: CRITICAL: polkit_authority_check_authorization: assertion `POLKIT_IS_AUTHORITY (authority)' failed
Jul  9 12:00:09 localhost console-kit-daemon[597]: CRITICAL: polkit_authority_check_authorization: assertion `POLKIT_IS_AUTHORITY (authority)' failed
Jul  9 12:00:10 localhost console-kit-daemon[597]: CRITICAL: polkit_authority_check_authorization: assertion `POLKIT_IS_AUTHORITY (authority)' failed
Jul  9 12:00:29 localhost dbus[471]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
Jul  9 12:00:34 localhost dbus[471]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Jul  9 12:00:34 localhost dbus[471]: [system] Successfully activated service 'org.freedesktop.UPower'
Jul  9 12:00:34 localhost dbus[471]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Jul  9 12:00:34 localhost dbus[471]: [system] Successfully activated service 'org.freedesktop.UPower'
Jul  9 12:00:34 localhost dbus[471]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Jul  9 12:00:35 localhost dbus[471]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Jul  9 12:00:35 localhost dbus[471]: [system] Successfully activated service 'org.freedesktop.UPower'
Jul  9 12:00:35 localhost dbus[471]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Jul  9 12:00:35 localhost dbus[471]: [system] Successfully activated service 'org.freedesktop.UPower'
Jul  9 12:00:59 localhost dbus[471]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Jul  9 12:00:59 localhost dbus[471]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Jul  9 12:01:24 localhost dbus[471]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Jul  9 12:01:24 localhost dbus[471]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Jul  9 12:01:49 localhost dbus[471]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Jul  9 12:02:30 localhost dbus[471]: [system] Reloaded configuration
Jul  9 12:02:30 localhost dbus[471]: [system] Reloaded configuration
Jul  9 12:02:30 localhost dbus[471]: [system] Reloaded configuration
Jul  9 12:02:30 localhost dbus[471]: [system] Reloaded configuration
Jul  9 12:04:17 localhost dhcpcd[955]: version 5.5.6 starting
Jul  9 12:04:17 localhost dhcpcd[955]: eth0: waiting for carrier
Jul  9 12:04:19 localhost dhcpcd[955]: eth0: carrier acquired
Jul  9 12:04:19 localhost dhcpcd[955]: eth0: sending IPv6 Router Solicitation
Jul  9 12:04:19 localhost dhcpcd[955]: eth0: sendmsg: Cannot assign requested address
Jul  9 12:04:19 localhost dhcpcd[955]: eth0: rebinding lease of 10.42.0.65
Jul  9 12:04:19 localhost dhcpcd[955]: eth0: acknowledged 10.42.0.65 from 10.42.0.1
Jul  9 12:04:19 localhost dhcpcd[955]: eth0: checking for 10.42.0.65
Jul  9 12:04:23 localhost dhcpcd[955]: eth0: sending IPv6 Router Solicitation
Jul  9 12:04:24 localhost dhcpcd[955]: eth0: leased 10.42.0.65 for 3600 seconds
Jul  9 12:04:24 localhost dhcpcd[955]: forked to background, child pid 987
Jul  9 12:04:26 localhost dhcpcd[990]: dhcpcd already running on pid 987 (/run/dhcpcd-eth0.pid)
Jul  9 12:04:27 localhost dhcpcd[987]: eth0: sending IPv6 Router Solicitation
Jul  9 12:04:31 localhost dhcpcd[987]: eth0: sending IPv6 Router Solicitation
Jul  9 12:04:31 localhost dhcpcd[987]: eth0: no IPv6 Routers available
Jul  9 16:09:11 localhost console-kit-daemon[597]: CRITICAL: polkit_authority_check_authorization: assertion `POLKIT_IS_AUTHORITY (authority)' failed
Jul  9 16:09:36 localhost console-kit-daemon[597]: CRITICAL: polkit_authority_check_authorization: assertion `POLKIT_IS_AUTHORITY (authority)' failed
Jul  9 16:10:01 localhost dbus[471]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Jul  9 16:10:01 localhost dbus[471]: [system] Successfully activated service 'org.freedesktop.UPower'
Jul  9 16:11:34 localhost init: Switching to runlevel: 6

venam · 2012-07-10 05:14:51

Hello Psyconaughty,
Can you try to connect manually to see if the problem is from wicd or from your driver or NIC itself.
Here is how to do that depending on the security (encryption) of your router:
Test Networking:
identify NIC => lspci | grep -i net
iwconfig
if error check => /usr/bin/dmesg or dmesg | grep firmware
firware => /lib/firmware (see the installed firmware)
Getting the list of ESSID => iwlist wlan0 scan
for WPA:
encrypt the pass and ESSID => wpa_passphrase "myESSID" "mysecretpass" > /etc/wpa_supplicant.conf
wpa_supplicant -B -i wlan0 -Dwext -W
ifconfig wlan0 192.168.0.205 netmask 255.255.255.0 broadcast 192.168.0.255 up
route add default gw 192.168.0.1
WEP => iwconfig wlan0 essid "thename"
NOENCRYPTION => iwconfig wlan0 essid "thename"
start network manager => /etc/rc.d/networkmanager start
check if connected => iwconfig wlan0

I really hope this will help you.

JackH79 · 2012-07-10 08:55:46

iwconfig is deprecated. Use iw instead. Then you can simply

ip link set wlan0 up
iw wlan0 connect <my network>
dhcpcd wlan0

If you don't know your network, you can also use

iw wlan0 scan | grep SSID

swanson · 2012-07-10 09:01:23

netcfg and net-auto-wireless are also good bets. I recently changed from a long time with wicd to net-auto-wireless. It works better but isn't as easy to use as wicd.

Psyconaughty · 2012-07-10 17:30:24

EDIT: Nevermind I was able to connect through wpa_gui.

Last edited by Psyconaughty (2012-07-10 19:07:09)

kasinathps · 2019-03-21 05:09:49

you need both wicd and wicd-gtk installed

the just do

systemctl enable wicd

if non root user then add sudo

worked for me

Last edited by kasinathps (2019-03-21 05:11:32)

jasonwryan · 2019-03-21 05:53:03

Thread is seven years old: no-one cares.

Read the Code of Conduct: https://wiki.archlinux.org/index.php/Co … bumping.22

Closing

Arch Linux

#1 2012-07-09 03:04:43

WICD "Could not connect to wicd's D-bus interface"

#2 2012-07-09 04:07:28

Re: WICD "Could not connect to wicd's D-bus interface"

#3 2012-07-09 04:22:36

Re: WICD "Could not connect to wicd's D-bus interface"

#4 2012-07-09 05:05:31

Re: WICD "Could not connect to wicd's D-bus interface"

#5 2012-07-09 08:46:56

Re: WICD "Could not connect to wicd's D-bus interface"

#6 2012-07-09 16:39:19

Re: WICD "Could not connect to wicd's D-bus interface"

#7 2012-07-09 19:15:52

Re: WICD "Could not connect to wicd's D-bus interface"

#8 2012-07-09 21:31:19

Re: WICD "Could not connect to wicd's D-bus interface"

#9 2012-07-10 05:14:51

Re: WICD "Could not connect to wicd's D-bus interface"

#10 2012-07-10 08:55:46

Re: WICD "Could not connect to wicd's D-bus interface"

#11 2012-07-10 09:01:23

Re: WICD "Could not connect to wicd's D-bus interface"

#12 2012-07-10 17:30:24

Re: WICD "Could not connect to wicd's D-bus interface"

#13 2019-03-21 05:09:49

Re: WICD "Could not connect to wicd's D-bus interface"

#14 2019-03-21 05:53:03

Re: WICD "Could not connect to wicd's D-bus interface"

Board footer