Steps to Reproduce: 1. login as a non-root user 2. open nm-connection-editor from applet 3. add a (wired|vpn) connection Actual results: error - cannot add the connection Expected results: success Additional info: Try it again and it works. Reproduced twice, after restarting the OS.
Are you checking the "Available for all users" box? Also, please try this update: NetworkManager-0.7.1.998-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10696
Related bug in Fedora 12; making a vpn setup(non-root) the first time goes fine but when later trying to change security and authentication under the advanced PPTP options it will not save the changes(always falls back to no MPPE and 128-bit and no stateful encryption, and unable to disable authentication on PAP, CHAP, EPA(only using MSCHAPv2)), compression and echo options are not affected. No error message is given. Checking "Available for all users" box will not help. However establishing a vpn connection shows in the logs that: "localhost pppd[8481]: CHAP authentication succeeded localhost pppd[8481]: MPPE 128-bit stateless compression enabled" Exporting vpn configuration will not work and gives error message, "unknown error".
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(In reply to comment #2) > Related bug in Fedora 12; making a vpn setup(non-root) the first time goes fine > but when later trying to change security and authentication under the advanced > PPTP options it will not save the changes(always falls back to no MPPE and > 128-bit and no stateful encryption, and unable to disable authentication on > PAP, CHAP, EPA(only using MSCHAPv2)), compression and echo options are not > affected. No error message is given. Checking "Available for all users" box > will not help. Try this update (or a more recent one): https://admin.fedoraproject.org/updates/NetworkManager-0.7.2.996-1.fc11,NetworkManager-vpnc-0.7.2.996-1.fc11,NetworkManager-openconnect-0.7.2.996-1.fc11,NetworkManager-pptp-0.7.2.996-1.fc11,NetworkManager-openvpn-0.7.2.996-1.fc11 which includes some fixes to MPPE handling in the UI. You can do this by: yum --enablerepo=updates-testing update NetworkManager-pptp
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.