Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#65850 - [networkmanager-openvpn] Can't import OpenVPN configuration (can't detect key)

Attached to Project: Arch Linux
Opened by Anurak Jannawan (be99inner) - Monday, 16 March 2020, 06:47 GMT
Last edited by Jan Alexander Steffens (heftig) - Friday, 10 July 2020, 18:42 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No


Network Manager can't import OpenVPN configuration file.
when you import configuration, NetworkManager can't find key of client.

Additional info:
* package version(s): extra/networkmanager-openvpn 1.8.12-1
* openvpn farmat.

dev tun
proto udp
remote 1194
resolv-retry infinite
remote-cert-tls server
tls-version-min 1.2
verify-x509-name exmaple-name name
cipher AES-256-CBC
auth SHA256
verb 3
-----BEGIN OpenVPN Static key V1-----
-----END OpenVPN Static key V1-----

Steps to reproduce:
* Add new VPN.
* Import from file.
* Click import OpenVPN file
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Friday, 10 July 2020, 18:42 GMT
Reason for closing:  Fixed
Additional comments about closing:  libnma 1.8.30
Comment by Anurak Jannawan (be99inner) - Thursday, 26 March 2020, 07:12 GMT
I try to separate private and add manually add a private key to network manager setting,

First time, It's work on. But next time it's won't work because private key is lost from setting.
Comment by Manu (manujs) - Thursday, 26 March 2020, 10:17 GMT
I can also reproduce this behavior, as the private key option is forgotten, one cannot modify other VPN settings until a private key is re-added each time.
Comment by Anatoly Bashmakov (abashmakov) - Friday, 08 May 2020, 22:23 GMT
Seems like this behavior started with libnma version 1.8.28. Rolling back libnma to version 1.8.24 fixes the issue for me.
Comment by Anatoly Bashmakov (abashmakov) - Monday, 15 June 2020, 07:37 GMT Comment by Anatoly Bashmakov (abashmakov) - Friday, 10 July 2020, 10:00 GMT
Since libnma is updated to 1.8.30, I think the problem is fixed now.