Printable View
Hey Guys, I'm having the same problem after a fresh install of BT5-RC2 32bit gnome and I use a Atheros AR9285 driver. I can use aircrack tools like packet injection but a can't use it to connect to the internet with wicd? The above methods don't work for me. Has anyone figured out whats the problem?
Is the problem still present when launching Wicd on command-line?
melissabubble,
Open shell and do:Then try to click the GUI and wicd will open just fine. You can also adjust yer .bashrc to load it prior for u, that way when u click the gui it's already loaded on the backend.Code:wicd
I'm new to bt and I've just had the same problem. I reconfigure wicd, but I don't really think it changed anything. In my case it was the wrong combi of the WPA Supplicant Driver and ecryption method. Now everything works fine. Don't forget to check if your interface names in Preferences of wicd match.
its still not working after starting wicd from the command line and adjusting .bashrc. Does anyone no if using ubuntu network manager instead of wicd would break any packages?
Try reboot router
Ok so I'd get the same message using wicd, and it would crash and freeze a lot on me, but once I'd get it working and try and connect I'd get the same error so here is what I usually do to get past it:
a) Assign a static IP address, and if one is assigned I suggest that you change it, or if you manage to connect but get disconnected I suggest that you do a "Quick scan" of the whole subnet (if your connection lasts as long) to see if another user is using your IP)
b) Check that the encryption type is what it should be, a lot of times wicd would set the encryption to WPA 1/2 passphrase when it was a WEP encrypted network
c) Check your signal levels or do a re-scan of the networks to see if your card may have "missed" your station (you wouldn't believe how many times this happened)
I hope this helps someone.
As for the DBus error message, I'd notice I'd get that when I connect my external WiFi card post-boot, and since Wicd is set to use only that interface it would give me an error, a restart would usually fix that.
This fixed worked (and stuck) the first time. Thanks!
did mine the lazy way and added the wicd command to my startup apps list like what i had to do for the audio. got rid of the error message and now is auto connecting like it should.
Had the same error message popup every time I tried to use wicd. Didn't affect my ability to connect, I'd just fireup wicd and connect normally... Applied the fix below, error doesn't popup anymore. Thanks :)
Quote:
Originally Posted by sickness