Results 11 to 20 of 29
And you had no luck using WICD? Are you seeing any error messages with the dmesg command? Code: dmesg You might be able to grep it down a little bit ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 10-03-2009 #11
Are you seeing any error messages with the dmesg command?
dmesg | grep eth1
- 10-03-2009 #12
In fact, I have created another problem.
My computer suddenly always starts with the following error message.
Could not connect to wicd's D-Bus interface. Check the wicd log for error messages.
It's killing me. I liked WICD and I installed it on the HEALTHY computer as well. My both systems start with this message. Luckily I still have Internet access.Fedora20.GNOME@Dell_Latitude_E6410
- 10-03-2009 #13
Do you have dbus running on these machines?
Which distro are you using? See if you can find a program called "Services" and make sure DBUS and WICD are set to start on boot.
This post explains how he solved it, but he used YAST....I don't know if you have that.
Solved : Could not connect to wicd’s D-Bus interface | Spirit of Change
- 10-03-2009 #14
Yes I have YAST, but both services DBUS and WICD are started and running.
The distro I'm using is openSUSE 11.0 (on both machines).
By the way, the HEALTHY machine fixed itself. I don't know how, but I did do much, I just consumed some updates.
The problem is still present on the other machine. I'll try to do the same there.Fedora20.GNOME@Dell_Latitude_E6410
- 10-03-2009 #15
I have managed to start WICD again on FAULTY machine. However, my (until recently) HEALTHY machine suffers again form "Could not connect to wicd's D-Bus interface. Check the wicd log for error messages." (but this time I didn't do anything, only rebooted)
It appears that some of the consumed updates are affecting my NFS configuration. So I can't access my network drive any more from any of my machines.
I have to stop debugging my WPA problem and fix NFS first. Without network drive I'm crippled, all my files are there.Fedora20.GNOME@Dell_Latitude_E6410
- 10-03-2009 #16
I found a report of this being solved by adding the user to the "users" group.
useradd -G users username
- 10-04-2009 #17
Now, I have restored my both systems (from backups) in the previous state (as it was before WICD installation).
I believe that it is clear now that NetworkManager is not to blame. So I would prefer to continue debugging in my current configuration. I'll deal with WICD later when the WAP issue is fixed.
I also believe that wpa_supplicant.conf is all right, as my HEALTHY system worked with both NetworkMnager and WICD with his original wpa_supplicant.conf,
Please find the following links with the requested info:
- 10-04-2009 #18
- 10-04-2009 #19
- Join Date
- Jul 2004
I can't see any one thing that may be causing your problems either. You could try disabling any firewall, also disable SELinux.
When you tried Wicd, did you uninstall NetworkManager? You would need to uninstall it.
As a last resort, remove both Networkmanager and Wicd. Then connect by first setting up a proper wpa_supplicant.conf file. Then use the ifup/ifdown commands to control the wireless and wired connections. This is an option in the YaST Network configuration section.
The problem could also be in the wireless router/access point. Don't use WPA2 or AES, just use plain old WPA-TKIPPlease do not send Private Messages to me with requests for help. I will not reply.
- 10-04-2009 #20
- Join Date
- Jul 2004
One other thing:
ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheelPlease do not send Private Messages to me with requests for help. I will not reply.