Sorry for the confusion I caused by posting my "patch" earlier. This was completely bogus, so I removed it. The dbus config installed by network- manager-vpnc is correct. However, dbus just isn't seeing the new config file initially.
Re-reading this thread, it seems there may be a couple of bugs that people are having. The bug that I am seeing can be replicated like this: 1) Boot hardy live CD 2) Edit /etc/apt/sources.list and uncomment the universe repositories 3) Update and install vpnc $ sudo apt-get update $ sudo apt-get install vpnc network-manager-vpnc ** There's a bug in the NetworkManager dbus script that causes it not to restart properly in postinst - I did a quick look and didn't see this reported, so I guess I'll do this later. :-) NetworkManager must be restarted like this: $ sudo kill `cat /var/run/NetworkManager/NetworkManager.pid`; sleep 5; sudo /etc/dbus-1/event.d/25NetworkManager start 4) From nm-applet, VPN Connections -> Configure VPN... 5) Add a connection with appropriate settings for my Cisco VPN 6) Try to start the VPN from nm-applet VPN Connections -> MyVPN 7) Enter passwords and click OK At this point, there will be no change in the nm-applet icon, and no error messages, but the VPN will not connect. If you look in the syslog, you'll see messages like this: May 16 20:04:41 ubuntu NetworkManager: <info> Will activate VPN connection 'MyVPN', service 'org.freedesktop.NetworkManager.vpnc', user_name 'ubuntu', vpn_data 'IPSec gateway / vpn.somewhere.com / IPSec ID / GroupName / Xauth username / username', route ''. May 16 20:04:41 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 1 of 4 (Connection Prepare) scheduled... May 16 20:04:41 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 1 of 4 (Connection Prepare) ran VPN service daemon org.freedesktop.NetworkManager.vpnc (PID 10570) May 16 20:04:41 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 1 of 4 (Connection Prepare) complete. May 16 20:04:41 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 2 of 4 (Connection Prepare Wait) scheduled... May 16 20:04:42 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 2 of 4 (Connection Prepare Wait) waiting... May 16 20:04:42 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 2 of 4 (Connection Prepare Wait) scheduled... May 16 20:04:42 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 2 of 4 (Connection Prepare Wait) waiting... <snip> May 16 20:04:44 ubuntu NetworkManager: <info> VPN Activation (MyVPN) failed. May 16 20:04:44 ubuntu NetworkManager: <WARN> nm_vpn_service_stop_connection(): (VPN Service org.freedesktop.NetworkManager.vpnc): could not stop connection 'MyVPN' because service was 2. The reason for this seems to be that the file /etc/dbus-1/system.d/nm- vpnc-service.conf isn't being detected and re-read by dbus during the installation of network-manager-vpnc. If we force dbus to re-read it's config files: $ sudo /etc/init.d/dbus reload The vpn connection then works properly: May 16 20:12:43 ubuntu NetworkManager: <info> Will activate VPN connection 'MyVPN', service 'org.freedesktop.NetworkManager.vpnc', user_name 'ubuntu', vpn_data 'IPSec gateway / vpn.somewhere.com / IPSec ID / GroupName / Xauth username / username', route ''. May 16 20:12:43 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 1 of 4 (Connection Prepare) scheduled... May 16 20:12:43 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 1 of 4 (Connection Prepare) ran VPN service daemon org.freedesktop.NetworkManager.vpnc (PID 11055) May 16 20:12:43 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 1 of 4 (Connection Prepare) complete. May 16 20:12:43 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 2 of 4 (Connection Prepare Wait) scheduled... May 16 20:12:43 ubuntu NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' signaled state change 1 -> 6. May 16 20:12:43 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 2 of 4 (Connection Prepare Wait) waiting... May 16 20:12:43 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 2 of 4 (Connection Prepare Wait) complete. May 16 20:12:43 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 3 of 4 (Connect) scheduled... May 16 20:12:43 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 3 of 4 (Connect) sending connect request. May 16 20:12:43 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 3 of 4 (Connect) request sent, waiting for reply... May 16 20:12:43 ubuntu NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' signaled state change 6 -> 3. May 16 20:12:43 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 3 of 4 (Connect) reply received. May 16 20:12:43 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 4 of 4 (IP Config Get) timeout scheduled... May 16 20:12:43 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 3 of 4 (Connect) complete, waiting for IP configuration... May 16 20:12:45 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 4 of 4 (IP Config Get) reply received. May 16 20:12:46 ubuntu NetworkManager: <info> VPN Activation (MyVPN) Stage 4 of 4 (IP Config Get) complete. May 16 20:12:46 ubuntu NetworkManager: <info> VPN Activation (MyVPN) successful. May 16 20:12:46 ubuntu NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' signaled state change 3 -> 4. May 16 20:12:46 ubuntu NetworkManager: <debug> [1210968766.462818] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of VPN connection 'MyVPN' So, at least for the problem I am seeing - that connections fail at stage 2 of VPN Activation after initially installing vpnc and network- manager-vpnc - the solution is to force dbus to reload it's config. This can be easily done in the postinst script, so I'll put together a debdiff to do this - hopefully in the next few days. It may also make sense to open a new bug for this more narrow problem to avoid further confusion. I hope this helps everyone. Cheers! -- VPNC / Network-Manager couldn't connect https://bugs.launchpad.net/bugs/179239 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
