Description of problem: After importing a valid OVPN config file, the "User private key" remains unset, and the connection cannot be saved. Version-Release number of selected component (if applicable): NetworkManager-openvpn-gnome-1.8.12-1.fc32 How reproducible: Always Steps to Reproduce: 1. Open VPN settings panel. 2. Import some valid OVPN file. Actual results: The "User private key" variable remains unset showing the value "none". Expected results: The "User private key" variable is set to the correct value. Additional info: - When importing indivudal PEM files, then the VPN connection can be saved and activated successfully. However, when opening the corresponding configuration panel again, then "User private key" shows the value "none". The connection cannot be saved or updated unless the corresponding PEM file has been selected again. - This bug is a regression with respect to Fedora 31 for which valid OVPN configuration files can be imported flawlessly.
Same issue here.
(In reply to Alessio from comment #1) > Same issue here. In addition. If you add the key by hand, you are able to save the connection and it also work. But if you open the configuration in order to make some changes, you have to define the User private key again in order to be able to save the configuration.
Probably this is tracked upstream https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/50
It seems that it has been fixed upstream https://gitlab.gnome.org/GNOME/libnma/-/commit/b09c4dc2a8d3d7d44b9fc7ec22d499b7641de8c5
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.