[SOLVED] Wicd Could not connect to wicd's D-Bus interface
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. |
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. |
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] 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={ Code:
wpa_supplicant -B -iwlan0 -c/etc/wpa_supplicant.conf 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). |
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. |
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 |
Only do
$ sudo wicd
and configure your password then do $ wicd-gtk CYA |
Quote:
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 |
All times are GMT -5. The time now is 01:25 PM. |