I have my VPN connection set up via NetworkManager. That connection is set up to save the group password and prompt for the user password. If I open the configuration panel for the connection I can see that it has saved the correct group password. When I click on that VPN connection in the cinnamon NetworkManager applet menu, it should pop up a dialog that prompts for the user password only. It does this about 10% of the time. The other 90% of the time however, it prompts for both the user and group passwords. I'd open this against NM, but this never happens if I log into gnome-shell instead of cinnamon. In gnome-shell, it prompts for just the user password every time. I'm currently running: cinnamon-1.6.7-2.fc18.x86_64 NetworkManager-openconnect-0.9.7.0-1.git20120918.fc18.x86_64 NetworkManager-glib-0.9.7.0-9.git20121004.fc18.x86_64 NetworkManager-0.9.7.0-9.git20121004.fc18.x86_64 NetworkManager-pptp-0.9.3.997-3.fc18.x86_64 NetworkManager-vpnc-0.9.3.997-3.fc18.x86_64 NetworkManager-openvpn-0.9.3.997-3.fc18.x86_64 NetworkManager-devel-0.9.7.0-9.git20121004.fc18.x86_64 NetworkManager-glib-devel-0.9.7.0-9.git20121004.fc18.x86_64 ...let me know if there's other info I should provide.
I'm running into the same problem as Jeff, but I am always asked for both the user and group passwords. cinnamon-1.6.7-2.fc18.x86_64 NetworkManager-0.9.7.0-11.git20121004.fc18.x86_64 NetworkManager-pptp-0.9.3.997-3.fc18.x86_64 NetworkManager-openconnect-0.9.7.0-1.git20120918.fc18.x86_64 NetworkManager-vpnc-0.9.3.997-3.fc18.x86_64 NetworkManager-glib-0.9.7.0-11.git20121004.fc18.x86_64 NetworkManager-openvpn-0.9.3.997-3.fc18.x86_64
Post rpm -q network-manager-applet
$ rpm -q network-manager-applet network-manager-applet-0.9.7.0-6.git20121211.fc18.x86_64
Also present on F17, well reproducible (happens almost always). $ rpm -qa *vpn* NetworkManager-vpnc-0.9.3.997-1.fc17.i686 vpnc-script-0.5.3-14.svn457.fc17.noarch vpnc-0.5.3-14.svn457.fc17.i686 $ rpm -q network-manager-applet package network-manager-applet is not installed
This looks like a duplicate of bug 887879
Yep looks like it, let's close this as a dup of that for now. We can reopen it later if the problem is still present after that bug is resolved. *** This bug has been marked as a duplicate of bug 887879 ***