Description of problem: Somehow I ended up with some WPA Enterprise connections that have both "nma-path-ca-cert" and "ca-cert" gconf keys defined. I tried to change the CA certificate for one of these connections in nm-connection-editor, but after restarting nm-connection-editor, the old value came back. I dug a little in the source, and it looks like "nma-path-ca-cert" is from a previous version of NetworkManager and the editor is "migrating" the old value over and over again. Version-Release number of selected component (if applicable): NetworkManager-0.8.3.997-1.fc14 (Same bug in NetworkManager-0.8.1-10.git20100831.fc14) How reproducible: Always Steps to Reproduce: 1. Have an old WPA Enterprise connection with a CA certificate, or create one and manually add a "nma-path-ca-cert" key in gconf. 2. Open the connection editor and change the CA certificate. 3. Close and reopen the connection editor. Actual results: The CA certificate is back to the old value. Expected results: The CA certificate chosen in step 2 is retained.
145069e46e9e039cf8b113b6ca55090e7abdd628 (master) 8f1dce5152554b5bcececfef8832170fb1bbb0f6 (0.8.x)
NetworkManager-0.8.3.998-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/NetworkManager-0.8.3.998-1.fc14
NetworkManager-0.8.3.998-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.