Description of problem: When I add/remove/modify VPN service via NetworkManager menu "Network settings" item, I have to restart NetworkManager service (via systemctl restart NetworkManager.service) to change anything. Otherwise the NetworkManager menu reflects previous values. Version-Release number of selected component (if applicable): NetworkManager-gnome-0.8.9997-5.git20110702.fc16.x86_64 NetworkManager-0.8.9997-5.git20110702.fc16.x86_64 NetworkManager-glib-0.8.9997-5.git20110702.fc16.x86_64 NetworkManager-devel-0.8.9997-5.git20110702.fc16.x86_64 NetworkManager-openvpn-0.8.999-1.fc16.x86_64 NetworkManager-glib-devel-0.8.9997-5.git20110702.fc16.x86_64 How reproducible: 100% Steps to Reproduce: 1.see above 2. 3. Actual results: changes are not activated without the restart of the service Expected results: they should be, and I should have more ice cream Additional info:
In gnome shell, what happens if you Alt+F2, type 'r' and hit return? Does that make things show up as you expect? It could be a shell problem, or a libnm-glib problem, or an NM problem, so lets try to figure out which.
Created attachment 514077 [details] screencast of the reproduction Couple of comments to this screencast: 1) Notice that I had there VPN defined in the configuration editor, which wasn't visible in the NetworkManager menu (original RH VPN), 2) Notice that when clicking save in the configuration editor dialog, the name didn't change even in the configuration editor itself, 3) Notice that when clicking on the menu item itself, no dialog shows up (that's bug 723483), and 4) of course, I had to stitch this screencast from two pieces: after Alt+F2r<ENTER> recording stopped.
This is not fixed, changing the values for VPN is still mess. After a lot of restarting of everything I have managed to change "Ask always" value, but it still called ovpn2-ams-udp-x86_64 whatever I do.
network panel in control-center didn't refresh the info when a VPN connection was edited. As as workaround, it is sufficient to click 'All Settings' in control- center and then go back by clicking network icon, and all information is read again. However, the following patches fixes the bug and enhances VPN info a little.
Created attachment 514672 [details] Fix refreshing VPN info The patch fixes the bug
Created attachment 514673 [details] Enhance VPN info Display VPN info for all VPN types (not just vpnc)
Patches (comment #5 and comment #6) committed upstream. See https://bugzilla.gnome.org/show_bug.cgi?id=657303
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Why is this bug still just MODIFIED? Is the change propagated to other branches?
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days