Bug 240871

Summary:	vpnc crashes when called from knetworkmanager
Product:	[openSUSE] openSUSE 10.2	Reporter:	Mar Toss <martoss>
Component:	Network	Assignee:	Helmut Schaa <hschaa>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	32bit
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Networkmanager log with --no-daemon

Description Mar Toss 2007-01-31 20:31:07 UTC

vpnc runs fine from commandline. Same options provided in knetworkmanager

Get "could not start vpn connection LRZ"

part of /var/log/NetworkManager

Jan 31 20:48:38 orthanc NetworkManager: <info>  Updating VPN Connections...
Jan 31 21:00:44 orthanc NetworkManager: <info>  Will activate VPN connection 'LRZ', service 'org.freedesktop.NetworkManager.vpnc', user_name 'martin', vpn_data 'IPSec gateway / ipsec.lrz-muenchen.de / IPSec ID / mwnpda / Xauth username / mylogin@mydomain', route ''.
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN Activation (LRZ) Stage 1 of 4 (Connection Prepare) scheduled...
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN Activation (LRZ) Stage 1 of 4 (Connection Prepare) ran VPN service daemon org.freedesktop.NetworkManager.vpnc (PID 5882)
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN Activation (LRZ) Stage 1 of 4 (Connection Prepare) complete.
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN Activation (LRZ) Stage 2 of 4 (Connection Prepare Wait) scheduled...
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN service 'org.freedesktop.NetworkManager.vpnc' signaled state change 1 -> 6.
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN Activation (LRZ) Stage 2 of 4 (Connection Prepare Wait) waiting...
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN Activation (LRZ) Stage 2 of 4 (Connection Prepare Wait) complete.
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN Activation (LRZ) Stage 3 of 4 (Connect) scheduled...
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN Activation (LRZ) Stage 3 of 4 (Connect) sending connect request.
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN Activation (LRZ) Stage 3 of 4 (Connect) request sent, waiting for reply...
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN service 'org.freedesktop.NetworkManager.vpnc' signaled state change 6 -> 3.
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN Activation (LRZ) Stage 3 of 4 (Connect) reply received.
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN Activation (LRZ) Stage 4 of 4 (IP Config Get) timeout scheduled...
Jan 31 21:00:44 orthanc NetworkManager: <info>  VPN Activation (LRZ) Stage 3 of 4 (Connect) complete, waiting for IP configuration...
Jan 31 21:00:54 orthanc NetworkManager: <WARN>  nm_vpn_service_process_signal(): VPN failed for service 'org.freedesktop.NetworkManager.vpnc', signal 'ConnectFailed', with message 'The VPN login failed because the VPN program could not connect to the VPN server.'.
Jan 31 21:00:54 orthanc NetworkManager: <info>  VPN service 'org.freedesktop.NetworkManager.vpnc' signaled state change 3 -> 5.
Jan 31 21:00:54 orthanc NetworkManager: <info>  VPN service 'org.freedesktop.NetworkManager.vpnc' signaled state change 5 -> 6.
Jan 31 21:00:54 orthanc NetworkManager: <WARN>  nm_vpn_service_stop_connection(): (VPN Service org.freedesktop.NetworkManager.vpnc): could not stop connection 'LRZ' because service was 6.
orthanc:/var/log # kded: ERROR: : couldn't create slave : Kein Kontakt zu klauncher

Comment 1 Helmut Schaa 2007-03-28 10:12:33 UTC

Please run NetworkManager from the commandline with the argument "--no-daemon" to get a bit more detailed output and post it here. Thanks.

Comment 2 Stefan Behlert 2007-04-26 10:57:31 UTC

Mar, could you provide the requested information so we can proceed with the bug? Thanks!

Comment 3 Mar Toss 2007-04-27 08:44:58 UTC

Created attachment 135642 [details]
Networkmanager log with --no-daemon

I can confirm, that it works with the mentioned vpnc and Network Manager. The only problem that persists is that routing is not setup correctly, when vpnc is started from Network Manager, but this is probably another bug.
If i start vpnc from commandline, even the splitted routing is set up properly.

Comment 4 Helmut Schaa 2007-04-27 09:46:07 UTC

Thank you Mar.

Based on your info I assume this issue is fixed.
And for the routing problem, please file a new bug.