No problem with connecting nor import of OVPN file.
On my system, protonvpn-cli --get-logs works correctly with the nl_NL.UTF-8 .locale.
Could it be some localization problem? I do not see anything special in the OVPN but there should be some reason why you cannot import it.
NetworkManagger stores certificates in ~/.cert/nm-openvpn
Is this folder accessible? Does it work from a freshly created user account?
Do you have NetworkManager-openvpn-gnome installed? This at least could explain the blank openvpn import.
Proton from NetworkManager works perfect after import, but be sure to disable IPv6, if enabled, there is no ipv6 leak protection which is activated in protonvpn-cli or app.
Proton should add this package as dependency, protonvpn-cli fails too is this is missing.
Additional comment: “nmcli con up protonovpnconnection” does run without asking for the openvpn credentials if networkmanager-openvpn-gnome is installed, but requires the “–ask” option and password entry if it is not installed. Since Proton interacts with NetworkManager, one could argue whether this is a Proton, Fedora or upstream NetworkManager problem. The complexity of package dependencies almost forces third parties to distribute software as flatpak or container…
nm-connection-editor works on lxqt, so I assume NetworkManager-openvpn-gnome works too, if all necessary libraries are loaded as dependency.
In this case, it looks like NetworkManager-openvpn and NetworkManager-openvpn-gnome are such related that the functionality of a command-line program changes.
Question for the packagers: should openvpn-gnome added as dependency, forcing installation of a lot of gnome software on a server system…
Would it not make more sense, to add on https://github.com/ProtonVPN/linux-cli
A note, that for small footage fedora versions, a gnome pendency would be needed and has to be installed separately, making protonvpn-cli working?
As we talked about the protonvpn-cli here.
Sorry, it is not so easy to file bug reports there.
The problem is “/usr/libexec/nm-openvpn-auth-dialog”, if this file is present, the software works. The program source is in the “networkmanager-openvpn” git.
Fedora has only one source RPM including both "networkmanager-openvpn’ and “networkmanager-openvpn-gnome” The SPEC file directs nm-openvpn-auth-dialog to the “networkmanager-openvpn-gnome” rpm. So this seems not 100% correct, but including this file in the other rpm might introduce unnecessary dependencies in many cases. Simplest solution would be to make it dependency in the proton package, there it’s needed. According to rpmfind.net, most or all rpm-based distributions pack the program in the nm-openvpn-gnome.