wpa psk key not updated in kwallet after changing it

[sk0rp10]

Binary package hint: knetworkmanager

Version : latest @ Feisty
Reproducibility : always

Changing the WPA-PSK of a certain wireless network, and then using the "connect to other network" option of knetworkmanager to manually insert the newly configurated wpa-psk works, and knetworkmanager succesfully connects using the new PSK, but it does not change the old value stored in kwallet , so on next access to the wireless network it uses the old obsolete value.

I think it should perform a check after using the "connect to other networks" based on the ESSID and eventually update stored data.

[Rich Johnson (nixternal)]

I can confirm this with Feisty up to date.

[Jared Sutton (jpsutton)]

I think my issue is the same. On connecting to a given network for the first time, everything works great. However, the next time I go to connect to that network, it always fails. Using the "Connect to other network" option does work (but that gets really old really fast :) ). I've observed this behavior on a WPA-PSK network (at home) and a WPA Enterprise setup (at work). I'm running the latest updates on Feisty.

[Sokraates (sokraates)]

I have exactly the same problem with WEP-keys. I used the combination of ndiswrapper, knetworkamanger and kwallet since Dapper on my HP nx6110 (Broadcom 4318 rev2). Only with Feisty do I have this problem. Before Feisty I used WPA-PSK, but this no longer works (several bugs filed). Although th problem seems to have appeared only this week, since I installed Feisty beta on Saturday (31.03.2007) and until, I think, Monday the automatic connection worked.

[Sokraates (sokraates)]

After some tries I managed to solve the issue by deleting the entry for my network from kwallet. Deleting the password was not enough. Then I used knetworkmanager to connect to my network and kwallet furtheron remembered the correct key.

[Dennis Nienhüser (earthwings)]

Same happens when changing authentication type e.g. from WEP to WPA (like I just did with my router). It didn't remember the new settings (I connected using the "Connect to other wireless network" option) and I had to delete the old entry from ~/.kde/share/config/knetworkmanagerrc.

[Jonathan Thomas (echidnaman)]

Thank you for taking the time to report this bug and helping to make Kubuntu better. The KDE3 version of KNetworkManager has been discontinued by its original authors. This unfortunately means that there will be no more bugfix releases, and updates in general will be limited to those fixing security flaws.

While we cannot fix your bug, the good news is that the applet has been totally rewritten for KDE4 in the upcoming Kubuntu 9.10 release. There is a good chance that this bug is no longer an issue with the new applet. If you find any similar or new issues with the applet included in Kubuntu 9.10, we would politely ask you to file them as new bugs against the "plasma-widget-networkmanagement" package.

Thanks in advance for your cooperation and understanding.