Bug 399012

Summary:	plasma-nm imports wrong 'TCP connection' setting from openvpn file
Product:	[Applications] systemsettings	Reporter:	Benjamin Wiese <benjamin.wiese>
Component:	kcm_networkmanagement	Assignee:	Jan Grulich <jgrulich>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	heri+kde, jgrulich
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Benjamin Wiese 2018-09-24 09:56:46 UTC

SUMMARY
plasma-nm imports wrong 'TCP connection' setting from openvpn file

STEPS TO REPRODUCE
1. Create an openvpn file foo.ovpn where the 'Use a TCP connection' setting is set by using the flag 'tcp-client' with 'remote', e.g.: remote 212.204.68.178 443 tcp-client. Make sure there is also a .p12 and a .key file in the same directory.

2. Open the "Networks" widget from the Task Manager by clicking on the widget (the widget's icon on the Task Manager is a wifi-symbol on most systems)

3. Click the "Configure the network connections..." in the top right of the widget window

4. Click the "Add new connection" in the bottom left of the new window

5. Select the "Import VPN connection..." from the bottom of the list and click the "Create" button

6. Browse to the .ovpn file and click the "Open" button

7. Click the "Yes" button in the "Copy certificates - System Settings Module" window that pops up 

EXPECTED RESULT
All settings from the .ovpn file are imported correctly, especially the checkbox 'Use a TCP Connection' is checked (select the VPN connection -> VPN tab -> Advanced -> General)

ACTUAL RESULT
The checkbox 'Use a TCP Connection' is not checked.


SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
A collegue reproduced this bug with Plasma 5.8.9 on Kubuntu 16.04.

Comment 1 Dennis Schridde 2018-12-28 13:53:46 UTC

I think this stems from the root cause of not using the NetworkManager OpenVPN importer, which bug #396530 deals with.

Comment 2 Justin Zobel 2023-01-19 00:18:57 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 3 Bug Janitor Service 2023-02-03 05:01:32 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Bug Janitor Service 2023-02-18 03:47:33 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!