Comment 56 for bug 360818

"Me too". Karmic beta, fully up-to-date. Trying to connect using network-manager-vpnc, the message is that the "VPN service stopped unexpectedly".

I installed yesterday, and yesterday a reboot fixed the problem. From yesterday, I have a number of messages in auth.log as follows:

{{{
Oct 6 15:51:13 michael-laptop dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.4" (uid=0 pid=986 comm="NetworkManager) interface="org.freedesktop.NetworkManager.VPN.Plugin" member="NeedSecrets" error name="(unset)" requested_reply=0 destination="org.freedesktop.NetworkManager.vpnc" (uid=0 pid=2858 comm="/usr/lib/network-manager-vpnc/nm-vpnc-service))
Oct 6 15:51:13 michael-laptop dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.4" (uid=0 pid=986 comm="NetworkManager) interface="org.freedesktop.NetworkManager.VPN.Plugin" member="Disconnect" error name="(unset)" requested_reply=0 destination="org.freedesktop.NetworkManager.vpnc" (uid=0 pid=2858 comm="/usr/lib/network-manager-vpnc/nm-vpnc-service))
}}}

Today I am unable to connect with the same bubble message, but nothing in auth.log. Today, I have messages in daemon.log like the following:

{{{
Oct 7 11:41:53 michael-laptop NetworkManager: <info> Starting VPN service 'org.freedesktop.NetworkManager.vpnc'...
Oct 7 11:41:53 michael-laptop NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 1944
Oct 7 11:41:53 michael-laptop NetworkManager: <WARN> vpn_service_watch_cb(): VPN service 'org.freedesktop.NetworkManager.vpnc' exited with error: 1
Oct 7 11:41:53 michael-laptop NetworkManager: <info> (wlan0): writing resolv.conf to /sbin/resolvconf
Oct 7 11:41:53 michael-laptop NetworkManager: <info> Policy set 'Auto fritz.box' (wlan0) as default for routing and DNS.
Oct 7 11:41:59 michael-laptop NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' did not start in time, cancelling connections
}}}

I couldn't find any root shells, and the at_console thing didn't help either. I got messages like the above both before and after applying the at_console patch and rebooting.