The issue was reported upstream and they commented
"the plugin doesn't use --daemon, so it's unclear why the quoted message would matter.
It looks like the plugin is unable to re-request the password. So, having openvpn cache the password might workaround the issue in some cases, but it doesn't seem to be the right fix.
Maybe it's due to --user, and later the plugin's /usr/libexec/nm-openvpn-service-openvpn-helper is unable to connect NetworkManager via D-Bus.
Or maybe, openvpn requests a new secret via the --management socket, but the plugin fails to handle the request.
It would be helpful to provide a logfile with full debugging info enabled (beware of private data!!).
On recent versions, you can enable verbose logging via
sudo nmcli general logging level TRACE domains ALL,VPN_PLUGIN
The issue was reported upstream and they commented
"the plugin doesn't use --daemon, so it's unclear why the quoted message would matter.
It looks like the plugin is unable to re-request the password. So, having openvpn cache the password might workaround the issue in some cases, but it doesn't seem to be the right fix.
Maybe it's due to --user, and later the plugin's /usr/libexec/ nm-openvpn- service- openvpn- helper is unable to connect NetworkManager via D-Bus.
Or maybe, openvpn requests a new secret via the --management socket, but the plugin fails to handle the request.
It would be helpful to provide a logfile with full debugging info enabled (beware of private data!!).
On recent versions, you can enable verbose logging via
sudo nmcli general logging level TRACE domains ALL,VPN_PLUGIN
and re-activate the connection. /cgit.freedeskt op.org/ NetworkManager/ NetworkManager/ plain/contrib/ fedora/ rpm/NetworkMana ger.conf? id=master"
See https:/