network manager editor does update the keyring

[Charles Timko]

Running: Ubuntu Hardy (development branch)
Release: 8.04
Issue: Network Manager Editor
Description of Issue: Network Manager Editor doesn't seem to update the keyring. For example, I can't just click on a network that I have already connected to because the data that is saved in the keyring is wrong. So, I remove the connection from the Network Manager Editor, and then I can click on the network and insert the passphrase. The problem is this. The next time I open the Network Manager Editor, the settings are changed back to the older version which includes the wrong passphrases. When I am already connected to a network and then I check the MNE and close it, it changes all the passphrases to the previous versions...
Current Solution: Not using the Network Manager Editor.

[Konrad Paumann (kopa)]

I can confirm this problem.

[Jo (cokhavim)]

I also confirm this for the current stable release of Ubuntu Hardy.

[Gaussian (saku)]

I can confirm this behavior on up to date Intrepid. Also, see
http://ubuntuforums.org/showthread.php?t=921064

for two other users confirming this on Intrepid

[Tatty (tatter-sall)]

I am having this problem too with a fresh install of Intrepid (amd64) from a daily build iso.

[Tatty (tatter-sall)]

Just to add, for me this behaviour appears on the normal network manager connection dialog to, not just when using the NM connection editor.

As I am using a fresh install, i simply have no passwords saved, as opposed to any old passwords reappearing. When running nm-applet from a terminal therefore i always get:

tatty@tatty-laptop:~$ nm-applet
** Message: <info> No keyring secrets found for Auto LordTatty/802-11-wireless-security; asking user.

But no other error messages appear.

[lemonade (lemonade)]

I can confirm this too. Network Manager doesn't seem to save any passwords to keyring - instead it always asks user.

[beudbeud (beudbeud)]

I can confirm this problem. Network Manager doesn't save my key WEP

[jackocleebrown (jack-ocleebrown)]

I also see this behavior.

[leandro (drkthrn)]

Same problem here.
Just confirming this problem.

[Ralph Wabel (rwabel)]

I confirm that bug for ubuntu 8.10, it doesn't store my WPA key

[Marcos Hernández Blanco (kchopein)]

Same problem here!

[Taylor "Ripps" LeMasurier-Wren (ripps818)]

same problem too.
Kernel 2.6.27-4
rt2500 driver

[Michael Monreal (mimox)]

Well, "metoo" after installing a new system using the intrepid alpha6. Copied my old keyring over, no joy as the name under which the key is stored has changed from NM 0.6-NM0.7. Nice... I guess this will affect any user.

Stupid workaround of the day: get opensuse 11 (live cd), connect to the wlan(s) you use, copy the keyring to ubuntu => works

So other distributions manage to ship a non-broken NM, I hope Intrepid will not ship broken!

[Marcos Hernández Blanco (kchopein)]

Hi! I've just updated my system and after the reboot... the wifi connection works fine again!!

[jackocleebrown (jack-ocleebrown)]

After updates problem is fixed for me on Intrepid!

[lemonade (lemonade)]

I guess this can be changed to fixed as it is also working now for me in Intrepid with newest updates.

[SomeoneE1se (greg-grayhatter)]

this bug is back in the newest alpha of 10.4