[SOLVED] Wicd Could not connect to wicd's D-Bus interface

GreenFireFly · 07-15-2014, 06:34 PM

Hello Everyone,

I'm having a problem with wicd complaining about not being able to connect to dbus. Wicd was working fine earlier today.I have not done anything to my computer, so i dont know why it's acting up.

When i did ifconfig i can see my wlan0 and when i do iwlist wlan0 scan
i can see the access points. I tried doing

iwconfig wlan0 essid "network"
iwconfig wlan0 key *******
iwconfig wlan0 channel 1

but now what do i do next to get online. Please i need to know how
to do this from the command line cause it seems that network program
seem to act up fairly common.

frankbell · 07-15-2014, 06:59 PM

Could you post the exact wording of the error message?

Also, take a look in /var/log/wicd. You may find something useful there. If you do, post it to this thread, being sure to surround it with "code" tags for readability; they become available when you click the "Go Advanced" button to the right of the "Post Quick Reply" button at the bottom of the reply window.

bassmadrigal · 07-16-2014, 06:57 AM

If you're just looking at connecting to a wireless network via commandline, it depends on the network security. Unless things have changed since I last toyed around with wireless on Slackware iwconfig doesn't support WPA(2) and only supports WEP or unencrypted networks. If you are connecting to a WEP or unsecured network (which is pretty much a bad idea nowadays), you can simply run (replacing the bracketed pieces with information for your network -- if you don't have a network key, leave the key part off):

Code:

iwconfig wlan0 essid [your essid] key [wep key]
dhcpcd wlan0

You would need to run this as root and making sure that wlan0 is your network interface (from your above post it seems it is). Basically, the only thing left that you didn't do is ask the dhcp server for an IP address. Once you run dhcpcd wlan0, you should be online.

But if you are secured via WPA(2), you'll need to use wpa_supplicant. Edit the file /etc/wpa_supplicant and add the following:

Code:

network={
            ssid="ssid_name"
             psk="password"
}

You would then run (as root):

Code:

wpa_supplicant -B -iwlan0 -c/etc/wpa_supplicant.conf
dhcpcd wlan0

For a quick dive into wireless networking, see http://docs.slackware.com/slackbook:wifi. If you want a more in depth version, check out http://alien.slackbook.org/dokuwiki/...ckware:network

Personally, I never ended up using wicd, as it seemed when it was first introduced that it wouldn't stay connected for me either. I ended up just setting up my wpa_supplicant file and then modified /etc/rc.d/rc.inet1.conf to connect to that network (covered in the second link). Granted, this was probably 3 years ago (and I'd imagine things are much better than back then). It was probably right after wicd got introduced as a standard package instead of just in the extra/ directory. Now, all my computers are hard wired except for my laptop, but that has a weird hardware configuration that isn't very friendly to Linux (at least it wasn't last I looked).

GreenFireFly · 07-16-2014, 08:45 AM

Hello Everyone,

Frankbell - There was nothing useful in the wicd.log. The message i get is
Could not connect to wicd's D-Bus interface. Which then tells me to Please
check that the wicd service is running. So i did /etc/rc.d/rc.wicd start
which tells me it is already started.

Bassmadrigal - Thanks i needed to use the wpa_supplicant.At least now i can connect to the internet until i can figure out whats wrong with wicd.

GreenFireFly · 07-16-2014, 08:24 PM

Hello Everyone,

Ok i solved my wicd problem. It seems that when i tried to do /rc.d/rc.wicd stop it was doing a trackback and would not stop. So i did a /rc.d/rc.wicd
restart then /rc.d/rc.wicd stop that finally stop wicd then i just did /rc.d/rc.wicd start and then started wicd-client.

Code:

bash-4.2# /etc/rc.d/rc.wicd stop
Stopping wicd daemon and closing connections...
Traceback (most recent call last):
  File "/usr/share/wicd/daemon/wicd-daemon.py", line 1849, in <module>
    main(sys.argv)
  File "/usr/share/wicd/daemon/wicd-daemon.py", line 1760, in main
    bus = dbusmanager.connect_to_dbus()
  File "/usr/lib64/python2.7/site-packages/wicd/dbusmanager.py", line 48, in connect_to_dbus
    return DBUS_MANAGER.connect_to_dbus()
  File "/usr/lib64/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/lib64/python2.7/site-packages/dbus/bus.py", line 241, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 248, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib64/python2.7/site-packages/dbus/bus.py", line 180, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib64/python2.7/site-packages/dbus/bus.py", line 278, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib64/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
bash-4.2# /etc/rc.d/rc.wicd restart
Stopping wicd daemon...
Starting wicd daemon: /usr/sbin/wicd &
bash-4.2# /etc/rc.d/rc.wicd stop
Stopping wicd daemon and closing connections...
bash-4.2# /etc/rc.d/rc.wicd start
Starting wicd daemon: /usr/sbin/wicd &

blackunix · 04-29-2019, 06:40 AM

$ sudo wicd
and configure your password
then do
$ wicd-gtk
CYA

bassmadrigal · 04-29-2019, 12:48 PM

Quote:

Originally Posted by blackunix

$ sudo wicd
and configure your password
then do
$ wicd-gtk
CYA

This is a post in the Slackware subforum (that's almost 5 years old), and Slackware doesn't have sudo set up by default.

And wicd on Slackware should be started by passing start to the startup script, /etc/rc.d/rc.wicd

Code:

/etc/rc.d/rc.wicd start