After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 793366 - NetworkManager: Imported OpenVPN connections fail when import filename contains a space
NetworkManager: Imported OpenVPN connections fail when import filename contai...
Status: RESOLVED DUPLICATE of bug 793910
Product: NetworkManager
Classification: Platform
Component: VPN: openvpn
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2018-02-11 19:05 UTC by Steve Deprey
Modified: 2018-03-07 16:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Steve Deprey 2018-02-11 19:05:35 UTC 
Using the NetworkManager GUI to import a .ovpn file. If the file name contains a space, this bug will be triggered.

The file is imported successfully, but upon attempting to connect it immediately fails. The following error messages show up in the journal:

nm-openvpn[2864]: Options error: --ca fails with '/home/user/.cert/nm-openvpn/imported%20file-ca.pem': No such file or directory (errno=2)
nm-openvpn[2864]: Options error: --cert fails with '/home/user/.cert/nm-openvpn/imported%20file-cert.pem': No such file or directory (errno=2)
nm-openvpn[2864]: WARNING: cannot stat file '/home/user/.cert/nm-openvpn/imported%20file-key.pem': No such file or directory (errno=2)
Janm-openvpn[2864]: Options error: --key fails with '/home/user/.cert/nm-openvpn/imported%20file-key.pem': No such file or directory (errno=2)

The import process is converting the spaces to %20 and causing the above errors.
Comment 1 Beniamino Galvani 2018-03-07 16:14:44 UTC 
This is probably a duplicate of bug 793910, now fixed.

*** This bug has been marked as a duplicate of bug 793910 ***