Can't connect to ProtonVPN (probably VPN in general)

[Łukasz Konieczny]

Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-37-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz
Memory: 15,6 GiB

network-manager version: 1.22.10-1ubuntu2.1

What happens?

I want to connect to VPN, no matter how I am doing so, be it using Plasma applet or via terminal (nmcli connection up se.protonvpn.com.udp), I can't. On the 4th June 2020 there was a network-manager update, and probably since this day I can't connect to VPN. Previously I could do so. Of course I have network-manager-openvpn installed, and ProtonVPN uses this method.
When I try to connect using terminal command, I have message to run "journalctl -xe NM_CONNECTION=59f16a8e-7dcb-4638-a810-8d07efe00fde + NM_DEVICE=wlp7s0".
When I run this, I've got warnings, which I have included in attachment "bug.txt".

What I expect?

I want to connect to VPN, like I used to earlier.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Jun 11 18:07:41 2020
InstallationDate: Installed on 2020-02-05 (126 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
IpRoute:
 default via 192.168.1.1 dev wlp7s0 proto dhcp metric 600
 169.254.0.0/16 dev wlp7s0 scope link metric 1000
 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.17 metric 600
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2020-05-04 (38 days ago)
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.22.10 connected started full enabled enabled enabled enabled enabled

[Sebastien Bacher (seb128)]

Thank you for your bug report. Could you start that command

$ journalctl -f

trigger the issue and add the log to the report?

[Łukasz Konieczny (panlukasz)]

@Sebastien Bacher

Hi.
I have run "nmcli connection up se.protonvpn.com.udp" and "journalctl -f" in another terminal window. The output is in file "journalctl_log.txt".

[Łukasz Konieczny (panlukasz)]

I must add, that I'm able to connect to this VPN using openvpn command. So this has to be a bug in NetworkManager.

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]