Wifi WPA2 Personnal not memorized

[Diti Torterat]

I run on Ubuntu Gutsy for the moment. The nm-applet can get me connected to WPA2 networks for now (it didn't work on Feisty).
But as I can't specify a default wifi network, I had to use manual configuration. To reproduce the bug:
• Select “manual configuration” on nm-applet ;
• Deactivate automatic mode and enter settings of a WPA2 network, while encryption is set to “WPA2 Personnal”. My password is an hexadecimal 10 characters-long ;
• You are connected. But now, log out, log in and go on the Internet. It doesn't works;
• Go to settings like some minutes ago. Then you will see that encryption is set to “WPA Personnal” and the password is very, very long (“•••••••••••••••••••••••••••••••••”).

[Diti Torterat (diti)]

So? Anything I can do for helping?

[Miguel Ruiz (mruiz)]

Hi,

I'm using NetworkManager with a WAP2 Personal encryption and I don't have problems. (Gutsy Gibbon up to date)

Can you add the content of '/var/log/syslog' (as attachment) after reproducing the bug ?

Tip -> https://wiki.ubuntu.com/DebuggingNetworkManager

Thanks in advance!

[Diti Torterat (diti)]

Hello,

As attachment, the system log which contains, on the first lines, the reason why (according to me) nm-applet ask for me to provide my key.
For information, securized network's SSID is called “PIERRAFEU” and the no-securized one is “FON_DITI”.

Thank you.

[Diti Torterat (diti)]

I reinstalled Ubuntu and it continues. Anything I can do to help?

[Mark Rijckenberg (markrijckenberg)]

Please follow these instructions to install and use wicd (wifi network manager):

http://wicd.sourceforge.net/download.php

Please let us know if wifi and WPA2 encryption works better using wicd

[Diti Torterat (diti)]

Well, Wicd is very good for WPA and WPA2, it connects me instantly without asking my keyring password twice ;) . But in the case I switch on WEP (because of my brother's Nintendo DS), there's no way to get it working...

And by the way, installing Wicd removes network-manager's nm-applet. Bad to reinstall if you can't connect to the network with Wicd.

And I tested : my original bug is not only for WPA2. Any stocked password... isn't stocked correctly.

[BeBop (daboyzbebop)]

I have exactly the same problem discribed for this bug ...

I upgraded to Hardy a week ago AND also installed packages "kubuntu-kde4-desktop" and "kde-l10n-fr" to test KDE4.

Problem appeared after my first login on KDE4.

I'm now obliged each time to (translate from french):

- click once on nm-applet icon,
- click on "Manual configuration",
- unlock,
- click on "Properties" for Wireless,
- change from "WPA" to "WPA2",
- re-renter the password,
- after waiting for connection, I can access WWW.

PS : If I try to check again nm-applet ... return to WPA.

[alelondon (alelondon)]

I have the same problem.
 As a clue i can say my system was initially Kubuntu (i wanted to try latest KDE) and then switched to ubuntustudio synaptic way.

i managed to not to have to type the password again if i stay on the same network/location adding to /etc/rc.local :

ifdown wlan0
ifup wlan0

but each time im away and back is not enough to change location. so i have to enter wpa2 pass again.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Diti Torterat (diti)]

Hmm, I don't have wifi any more, my USB wifi key doesn't work with Ubuntu versions more recent than v7.10 (I switched to Fedora a while ago because of that).

I'm going to use a live-CD and to see whether I can at least connect. If I can, I'll install Ubuntu and will tell you if that happens.

[Alexander Sack (asac)]

could you test live cd?

[Alexander Sack (asac)]

not an applet issue for sure. Most likely a driver timeout issue.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!