Hi Jayson. With a fully patched Hardy install this bug still exists as described in the initial report - using network-manager 0.6.6-0ubuntu5 and network-manager-gnome 0.6.6-0ubuntu3. Crash's posts seem to point to a possible problem with network-manager-gnome incorrectly reading, setting or manipulating the stored keys in system/networking/wireless/networks/<network name>.
I think the issue is related specifically to network-manager-gnome, but I can't offer any additional info without debugging assistance from the launchpad team. As a point of reference, the combination of network-manager 0.7~~svn20081018t105859-0ubuntu1.8.10.1 and network-manager-gnome v0.7~~svn20081020t000444ubuntu1 as deployed on a fully patched Intrepid system work as expected.
Hi Jayson. With a fully patched Hardy install this bug still exists as described in the initial report - using network-manager 0.6.6-0ubuntu5 and network- manager- gnome 0.6.6-0ubuntu3. Crash's posts seem to point to a possible problem with network- manager- gnome incorrectly reading, setting or manipulating the stored keys in system/ networking/ wireless/ networks/ <network name>.
I think the issue is related specifically to network- manager- gnome, but I can't offer any additional info without debugging assistance from the launchpad team. As a point of reference, the combination of network-manager 0.7~~svn2008101 8t105859- 0ubuntu1. 8.10.1 and network- manager- gnome v0.7~~svn200810 20t000444ubuntu 1 as deployed on a fully patched Intrepid system work as expected.