Public bug reported:
Ubuntu release: Ubuntu 18.04.1 LTS
Version of package: 1.8.2-1
Expected result: imported profile with space in name activates successfully
Actual result: activating profile fails immediately
As described in the title, when importing an OpenVPN profile with a
space in the name ("client (2).ovpn"), the certs were imported into
~/.cert/nm-openvpn/ properly and all appeared right in the GUI, but
activating the profile immediately failed.
Logs for nm-openvpn showed that it was attempting to find the cert with
its name URL-encoded, like "~/.cert/nm-openvpn/client%20(2)-ca.pem"
After renaming it without a space, importing and using the same profile
was successful.
I'm unsure if this is quite the right package to report against, so if
any further information is needed, let me know.
Thanks!
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager-openvpn 1.8.2-1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Aug 9 16:03:43 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-07-18 (387 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
SourcePackage: network-manager-openvpn
UpgradeStatus: Upgraded to bionic on 2018-07-31 (9 days ago)
** Affects: network-manager-openvpn (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1786356
Title:
Network Manager cannot find cert files for imported profile with space
in the name
Status in network-manager-openvpn package in Ubuntu:
New
Bug description:
Ubuntu release: Ubuntu 18.04.1 LTS
Version of package: 1.8.2-1
Expected result: imported profile with space in name activates successfully
Actual result: activating profile fails immediately
As described in the title, when importing an OpenVPN profile with a
space in the name ("client (2).ovpn"), the certs were imported into
~/.cert/nm-openvpn/ properly and all appeared right in the GUI, but
activating the profile immediately failed.
Logs for nm-openvpn showed that it was attempting to find the cert
with its name URL-encoded, like "~/.cert/nm-
openvpn/client%20(2)-ca.pem"
After renaming it without a space, importing and using the same
profile was successful.
I'm unsure if this is quite the right package to report against, so if
any further information is needed, let me know.
Thanks!
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager-openvpn 1.8.2-1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Aug 9 16:03:43 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-07-18 (387 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215)
SourcePackage: network-manager-openvpn
UpgradeStatus: Upgraded to bionic on 2018-07-31 (9 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1786356/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
