I’ve been struggling with fixing a nasty error with wicd network manager for about 2 hours.
The exact error message I faced was:
Connection Failed: Bad Password
The issue occured after some suggested updates from the Ubuntu graphical update tool.
The wireless network to which it was connected was a WPA-PSK (WPA2) Passphrase authentication.
The network key was properly typed in and was working well on another system so the error Connection Failed: Bad Password made no sense.
There was nothing unusual in /var/log/wicd/wicd.log , that made me even more curious about what might be causing the error.After a lot of try outs and a lot of readings and tests I finally got the cause of the weird Bad Password errors produced by wicd
Weirdly enought, somehow the Ubuntu package update tool has installed the default gnome network-manager package.
The installed network-manager package has mismatched somehow the way wicd connects to wireless networks and as a cause the wpa_supplicant binary was not properly invoked.
As a consequence of the network-manager being present on the system the wpa_supplicant process which made the exact connection to the wireless network was not launching in, the exact wpa_supplicant invocation missing was:
wpa_supplicant -B -i wlan0 -c /var/lib/wicd/configurations/0022b0aa424a -D wext
Luckily the solution to the notebook wireless device unable to connect to the Wireless network was simple.
All I had to do is completely remove all occurance of network-manager packages installed on the Ubuntu system, by issuing the commands:
ubuntu:~# apt-get remove --yes network-manager
ubuntu:~# dpkg --purge network-manager-pptp-gnome network-manager-pptp network-manager
The reason for issuing the a dpkg –purge command was my desire to completely get rid of all kind of network-manager related configurations.
Now after re-connecting with wicd wireless manager, it worked fine 😉
Tags: authentication, being, cause, consequence, default, dpkg, enought, exact connection, exact error message, Gnome, invocation, key, lib, log, manager, maverick, network key, occurance, occured, package, password errors, PasswordThe, purge command, reason, sense, supplicant, system, tool, try outs, Ubuntu, wicd, wireless networks, WPA, wpa supplicant, WPA-PSK, yes network
Thank you so much! I’ve been trying for awhile to get my wireless working again.
glad the tip helped. too bad this issue is still unfixed 🙁
hope to see you around.
best
Georgi
wicd is SO much better than the Gnome network manager. Many thanks for showing me how to get it working.
Hi Bob,
Yep wicd is a way, ahead. Let’s hope it will get better and better 😉
Wish you Best!
Georgi
It was related with network manager but that’s because wpa suplicant is being used more than once at same time.
I’ll explain:
First time when i got this error i digged all the foruns, all was pointing to be a problem with network-manager. It’s almost correct! What was happening was, as you said, wicd and n-man were both using wpa supplicant at same time. Well i never had any network manager on my dist, wicd was the default.
I looked at this:
“wpa_supplicant -B -i wlan0 -c /var/lib/wicd/configurations/0022b0aa424a -D wext”
it wasn’t really genuine, but i realised that wicd was loading all configuration files from /var/liv/wicd/configurations ( were 3 in my case ) and that would explain why i was able to connect sometimes after reboot and others don’t ( “loading lag”) and also why if i suspended or the connection died i couldn’t connect again.
This also explains why people with fresh install could resolve the connection problem after deleting network manager and those who had upgraded wicd couldn’t. ( old config being loaded ).
SOLUTION (plz update your post as it is very good and the reason i found this :P):
Delete all those configs!
Reboot!
Atleast worked for me and makes sence. Try and gimme some feedback.
Peace and Love.
Vitor, I tried your method, deleted all config files, rebooted, but wicd still says bad password.
I noticed that whenever a new wireless connection is established wicd creates a new config for that one.
Still struggling to figure out the root problem.
makes sense*
Thanks a lot!!
This approach worked for me!
Saved lot of work. Thanks!
very welcome 🙂
cya around
best
Thanks. Worked for me too.
Worked in crunchbang!
Thank you so much! Worked great!
Hi, didnt work for me. I'm using BT5R3 in Virtualbox. I applied the commands you served above, but it says that i havent got network-manager installed. And i still get the message "Bad Password.
I'm using a Usb-Network-Stick for the connection and got the following settings in VirtualBox:
Connected with: NAT
Adapter-type: Paravirtualnetwork (virtio-net)
Please help 🙁
My USB-Stick is: Netgear wnda4100 n900
i already installed the stick into BT5R3 by installing the chipset RT3573STA
Hi does all commands execute with no errors? I guess maybe in command
wpa_supplicant -B -i wlan0 -c /var/lib/wicd/configurations/0022b0aa424a -D wext
you need to change /var/lib/wicd/configurations/0022b0aa424a with your custom config?
Thank you!!!! Worked fine to me!
Thank you!