openvpn stopped to work between 2021-04-17 and 2021-04-27

Hi there,

Network manager/openVPN stopped to work between releases 2021-04-17 and 2021-04-27.
On 2021-04-17:

Operating System: openSUSE Tumbleweed 20210417
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
Kernel Version: 5.11.12-1-default
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-2350M CPU @ 2.30GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 3000


Installed snapshot version: 2021-04-17


 miguel $ nmcli con show
NAME                      UUID                                  TYPE      DEVICE 
rozsasnet                 213d566b-0101-4966-b9b6-9068de96d92a  wifi      wlp9s0 
apice                     14174e34-1da6-4aa9-98bb-cb6ca9d14f14  wifi      --     
apiceint                  f352792d-29e4-4046-8f19-8f77a89b2fa2  wifi      --     
cabeada dhcp generico     f51091a1-2a38-3211-b683-6d702d1ac221  ethernet  --     
HUAWEI Migs               748942e6-7867-4c35-9abb-00b7bfd1bca6  wifi      --     
Mezaros                   c2cb6782-303b-44c8-a908-eb5b004d03df  wifi      --     
publico                   5016e3c3-d1f7-49dd-9639-e97a1afcbccd  wifi      --     
SWAT_S                    7c903bd0-4843-4160-ac55-6d1ae658f3e2  wifi      --     
upsscanner                85621ee8-7a1b-48de-a0b4-fcc0bad08011  ethernet  --     
upsscanner cabeada union  996ac51d-0b62-4ec9-b120-8fe6ad2d18e8  ethernet  --     
voltronic cabeada padrao  3cc69b4e-7392-442d-9e15-61ec18ab7a6a  ethernet  --     
VPN apice                 8785122c-fe6b-48a3-9bc0-5f03f17a8861  vpn       --     
 miguel$ nmcli con up 8785122c-fe6b-48a3-9bc0-5f03f17a8861
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/4)
 miguel $ 


 
 miguel $ rpm -qa | grep -i networkmanager
NetworkManager-branding-openSUSE-42.1-3.8.noarch
libKF5NetworkManagerQt6-5.81.0-1.1.x86_64
NetworkManager-1.30.0-2.1.x86_64
NetworkManager-openvpn-1.8.12-2.6.x86_64
libproxy1-networkmanager-0.4.17-1.4.x86_64
NetworkManager-pptp-1.2.8-3.7.x86_64
NetworkManager-openconnect-gnome-1.2.6-3.6.x86_64
NetworkManager-openconnect-1.2.6-3.6.x86_64
NetworkManager-vpnc-1.2.6-3.6.x86_64
NetworkManager-vpnc-gnome-1.2.6-3.6.x86_64
NetworkManager-pptp-gnome-1.2.8-3.7.x86_64
NetworkManager-openvpn-gnome-1.8.12-2.6.x86_64


 miguel $nmcli con show
NAME                      UUID                                  TYPE      DEVICE 
VPN apice                 8785122c-fe6b-48a3-9bc0-5f03f17a8861  vpn       wlp9s0 
rozsasnet                 213d566b-0101-4966-b9b6-9068de96d92a  wifi      wlp9s0 
tun0                      24d2f9bc-309f-40c1-862d-68bf9a582d8f  tun       tun0   
apice                     14174e34-1da6-4aa9-98bb-cb6ca9d14f14  wifi      --     
apiceint                  f352792d-29e4-4046-8f19-8f77a89b2fa2  wifi      --     
cabeada dhcp generico     f51091a1-2a38-3211-b683-6d702d1ac221  ethernet  --     
HUAWEI Migs               748942e6-7867-4c35-9abb-00b7bfd1bca6  wifi      --     
Mezaros                   c2cb6782-303b-44c8-a908-eb5b004d03df  wifi      --     
publico                   5016e3c3-d1f7-49dd-9639-e97a1afcbccd  wifi      --     
SWAT_S                    7c903bd0-4843-4160-ac55-6d1ae658f3e2  wifi      --     
upsscanner                85621ee8-7a1b-48de-a0b4-fcc0bad08011  ethernet  --     
upsscanner cabeada union  996ac51d-0b62-4ec9-b120-8fe6ad2d18e8  ethernet  --     
voltronic cabeada padrao  3cc69b4e-7392-442d-9e15-61ec18ab7a6a  ethernet  --     
 miguel $nmcli con down 8785122c-fe6b-48a3-9bc0-5f03f17a8861
Connection 'VPN apice' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/4)
 miguel $

on 2021-04-27:

Operating System: openSUSE Tumbleweed 20210427
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
Kernel Version: 5.11.16-1-default
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-2350M CPU @ 2.30GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 3000


Installed snapshot version: 2021-04-27


 miguel $ nmcli con show
NAME                      UUID                                  TYPE      DEVICE 
rozsasnet                 213d566b-0101-4966-b9b6-9068de96d92a  wifi      wlp9s0 
apice                     14174e34-1da6-4aa9-98bb-cb6ca9d14f14  wifi      --     
apiceint                  f352792d-29e4-4046-8f19-8f77a89b2fa2  wifi      --     
cabeada dhcp generico     f51091a1-2a38-3211-b683-6d702d1ac221  ethernet  --     
HUAWEI Migs               748942e6-7867-4c35-9abb-00b7bfd1bca6  wifi      --     
Mezaros                   c2cb6782-303b-44c8-a908-eb5b004d03df  wifi      --     
publico                   5016e3c3-d1f7-49dd-9639-e97a1afcbccd  wifi      --     
SWAT_S                    7c903bd0-4843-4160-ac55-6d1ae658f3e2  wifi      --     
upsscanner                85621ee8-7a1b-48de-a0b4-fcc0bad08011  ethernet  --     
upsscanner cabeada union  996ac51d-0b62-4ec9-b120-8fe6ad2d18e8  ethernet  --     
voltronic cabeada padrao  3cc69b4e-7392-442d-9e15-61ec18ab7a6a  ethernet  --     
VPN apice                 8785122c-fe6b-48a3-9bc0-5f03f17a8861  vpn       --     
 miguel $ nmcli con up 8785122c-fe6b-48a3-9bc0-5f03f17a8861
Error: Connection activation failed: Unknown reason
Hint: use 'journalctl -xe NM_CONNECTION=8785122c-fe6b-48a3-9bc0-5f03f17a8861 + NM_DEVICE=wlp9s0' to get more details.
 miguel $

The output of ‘journalctl -xe NM_CONNECTION=8785122c-fe6b-48a3-9bc0-5f03f17a8861 + NM_DEVICE=wlp9s0’ can be found here https://pastebin.com/FyArBtFS

Hi
Update your system to the latest snapshot…


NAME="openSUSE Tumbleweed"
# VERSION="20210508"

To much water under the bridge from 20210407, 9 snapshots released…

Fair. Updated to the latest release:

cat /etc/issue.net  
Welcome to openSUSE Tumbleweed 20210511 - Kernel %r (%t).

but the prblem it is still around…


miguel $ nmcli con show
NAME                      UUID                                  TYPE      DEVICE  
rozsasnet213d566b-0101-4966-b9b6-9068de96d92awifiwlp9s0
apice                     14174e34-1da6-4aa9-98bb-cb6ca9d14f14  wifi      --      
apiceint                  f352792d-29e4-4046-8f19-8f77a89b2fa2  wifi      --      
BF4                       da366076-9657-4fa3-b044-d69283829afe  ethernet  --      
cabeada dhcp generico     f51091a1-2a38-3211-b683-6d702d1ac221  ethernet  --      
HUAWEI Migs               748942e6-7867-4c35-9abb-00b7bfd1bca6  wifi      --      
Mezaros                   c2cb6782-303b-44c8-a908-eb5b004d03df  wifi      --      
publico                   5016e3c3-d1f7-49dd-9639-e97a1afcbccd  wifi      --      
SWAT_S                    7c903bd0-4843-4160-ac55-6d1ae658f3e2  wifi      --      
UNION SOROCABA            f1060fc1-0365-4dcf-8bdb-465ccc231708  wifi      --      
upsscanner                85621ee8-7a1b-48de-a0b4-fcc0bad08011  ethernet  --      
upsscanner cabeada union  996ac51d-0b62-4ec9-b120-8fe6ad2d18e8  ethernet  --      
voltronic cabeada padrao  3cc69b4e-7392-442d-9e15-61ec18ab7a6a  ethernet  --      
VPN apice                 8785122c-fe6b-48a3-9bc0-5f03f17a8861  vpn       --      
**miguel $ **nmcli con up 8785122c-fe6b-48a3-9bc0-5f03f17a8861
Error: Connection activation failed: Unknown reason
Hint: use 'journalctl -xe NM_CONNECTION=8785122c-fe6b-48a3-9bc0-5f03f17a8861 + NM_DEVICE=wlp9s0' to get more details.

The affected packages now are:

rpm -qa | grep -i networkmanager
**NetworkManager**-openconnect-gnome-1.2.6-3.7.x86_64
**NetworkManager**-vpnc-gnome-1.2.6-3.7.x86_64
libKF5**NetworkManager**Qt6-5.82.0-1.1.x86_64
**NetworkManager**-pptp-gnome-1.2.8-3.8.x86_64
**NetworkManager**-pptp-1.2.8-3.8.x86_64
**NetworkManager**-1.30.4-1.1.x86_64
**NetworkManager**-openvpn-gnome-1.8.14-1.1.x86_64
**NetworkManager**-branding-openSUSE-42.1-3.9.noarch
**NetworkManager**-vpnc-1.2.6-3.7.x86_64
libproxy1-**networkmanager**-0.4.17-1.5.x86_64
**NetworkManager**-openvpn-1.8.14-1.1.x86_64
**NetworkManager**-openconnect-1.2.6-3.7.x86_64


Hi
Anything pop out in the hinted at journalctl command?

Nothing that caught my eye. The log is still available at NM/Openvpn fail - Pastebin.com. May be you can see what I am not seeing…
This should be a bug.
The current VPN definition was working untouched for almost 3 years, when the company VPN was created, it is not new. Look:

 ls -l Misc/openVPN/apice/1195/
total 8
-rw-r--r-- 1 miguel users 1769 out 27  2018 ca.crt
-rw-r--r-- 1 miguel users  172 nov 22  2018 client.ovpn


The only change was NetworkManager and the kernel itself somewhere after 2021-04-17.
Reverting to the previous snapshot restore my VPN access.
If it worth for anything, here is the openvpn config file:


\cat Misc/openVPN/apice/1195/client.ovpn   
client
dev tun
proto tcp
remote here-the-cia-ip-addr 1195
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.crt
verb 3
auth-user-pass
cipher AES-256-CBC

The only details on the problem in the log are:

NetworkManager[1056]: <info>  [1620674466.8460] vpn-connection...]: Started the VPN service, PID 2285
NetworkManager[1056]: <info>  [1620674466.8706] vpn-connection...]: Saw the service appear; activating connection
NetworkManager[1056]: <info>  [1620674467.2559] vpn-connection...]: VPN plugin: state changed: starting (3)
NetworkManager[1056]: <info>  [1620674467.2560] vpn-connection...]: VPN connection: (ConnectInteractive) reply received
NetworkManager[1056]: <warn>  [1620674467.2602] vpn-connection...]: VPN plugin: failed: connect-failed (1)
NetworkManager[1056]: <warn>  [1620674467.2603] vpn-connection...]: VPN plugin: failed: connect-failed (1)
NetworkManager[1056]: <info>  [1620674467.2604] vpn-connection...]: VPN plugin: state changed: stopping (5)
NetworkManager[1056]: <info>  [1620674467.2605] vpn-connection...]: VPN plugin: state changed: stopped (6)
NetworkManager[1056]: <info>  [1620674467.2641] vpn-connection...]: VPN service disappeared

And that is not enough information to see what is going wrong.
I think you should run openvpn from the command line to debug things, that ways it is easier to see problems and to enable more debugging but you need a .ovpn file for that.

Can you dump the Network Manager config for the VPN connection:

$ nmcli connection show 'VPN apice' | grep vpn.data

For me (with mine connection name) that outputs something like:

**vpn.data**:                               ca = /home/user/.local/share/networkmanagement/certificates/3F39-BBD7-D85B6C7E/ca.crt, cert = /home/user/.local/share/networkmanagement/certificates/3F39-BBD7-D85B6C7E/cert.crt, cert-pass-flags = 0, comp-lzo = yes, connection-type = tls, key = /home/user/.local/share/networkmanagement/certificates/3F39-BBD7-D85B6C7E/private.key, remote = my.ownvpn.org, reneg-seconds = 0

Then create an .ovpn file using:

$ nmcli connection show 'VPN apice' | perl -n -e 'if (m/^vpn.data:\s*(.*)/) {$_=$1; s/ = / /g; s/cert-pass-flags 0, //; s/connection-type tls, //; s/, /
/g; print "client
dev tun
verb 4
$_

"}' > debug.ovpn

$ cat debug.ovpn
client
dev tun
verb 4
ca /home/user/.local/share/networkmanagement/certificates/3F39-BBD7-D85B6C7E/ca.crt
cert /home/user/.local/share/networkmanagement/certificates/3F39-BBD7-D85B6C7E/cert.crt
cipher AES-256-CBC
comp-lzo yes
key /home/user/.local/share/networkmanagement/certificates/3F39-BBD7-D85B6C7E/private.key
port 443
remote my.ownvpn.org

The “cat” output above shows what is in the config file based on my earlier data.

Then run openvpn using:

$ sudo openvpn --verb 4 --config debug.ovpn

and share the output leaving out what you do not want to share.

I already had a opvn file (see the content at the end of previous post) that was used to create the NM VPN profile.
And it is working ! Look :

**kimera:~ #** openvpn --verb 4 --config ~miguel/Misc/openVPN/apice/1195/apice.ovpn
Fri May 14 08:50:01 2021 OpenVPN 2.4.10 x86_64-suse-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Dec  9 2020
Fri May 14 08:50:01 2021 library versions: OpenSSL 1.1.1k  25 Mar 2021, LZO 2.10
 Enter Auth Username: miguel
 Enter Auth Password: ***************          
Fri May 14 08:50:13 2021 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Fri May 14 08:50:13 2021 TCP/UDP: Preserving recently used remote address: [AF_INET]xx.xx.xx.xx:1195
Fri May 14 08:50:13 2021 Socket Buffers: R=[131072->131072] S=[16384->16384]
Fri May 14 08:50:13 2021 Attempting to establish TCP connection with [AF_INET]xx.xx.xx.xx:1195 [nonblock]
Fri May 14 08:50:14 2021 TCP connection established with [AF_INET]xx.xx.xx.xx:1195
Fri May 14 08:50:14 2021 TCP_CLIENT link local: (not bound)
Fri May 14 08:50:14 2021 TCP_CLIENT link remote: [AF_INET]xx.xx.xx.xx:1195
Fri May 14 08:50:14 2021 TLS: Initial packet from [AF_INET]xx.xx.xx.xx:1195, sid=06054ac7 6e8dc6de
Fri May 14 08:50:14 2021 VERIFY OK: depth=1, C=BR, ST=SP, L=Campinas, O=Apice, OU=Campinas, CN=obfuscated.com, name=obfuscated.com, emailAddress=ti@obfuscated.com
Fri May 14 08:50:14 2021 VERIFY OK: depth=0, C=BR, ST=SP, L=Campinas, O=Apice, OU=Campinas, CN=obfuscated.com, name=obfuscated.com, emailAddress=ti@obfuscated.com
Fri May 14 08:50:15 2021 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-CHACHA20-POLY1305, 2048 bit RSA
Fri May 14 08:50:15 2021 [obfuscate.com] Peer Connection Initiated with [AF_INET]xx.xx.xx.xx:1195
Fri May 14 08:50:16 2021 SENT CONTROL [obfuscate.com]: 'PUSH_REQUEST' (status=1)
Fri May 14 08:50:16 2021 PUSH: Received control message: 'PUSH_REPLY,route 192.168.160.0 255.255.255.0,dhcp-option DNS 192.168.160.211,dhcp-option DOMAIN obfuscate.com.local,persist-key,persist-tun,route 10.10.12.0 255.255
.255.0,topology net30,ping 10,ping-restart 120,ifconfig 10.10.12.26 10.10.12.25,peer-id 0,cipher AES-256-GCM'
Fri May 14 08:50:16 2021 OPTIONS IMPORT: timers and/or timeouts modified
Fri May 14 08:50:16 2021 OPTIONS IMPORT: --persist options modified
Fri May 14 08:50:16 2021 OPTIONS IMPORT: --ifconfig/up options modified
Fri May 14 08:50:16 2021 OPTIONS IMPORT: route options modified
Fri May 14 08:50:16 2021 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri May 14 08:50:16 2021 OPTIONS IMPORT: peer-id set
Fri May 14 08:50:16 2021 OPTIONS IMPORT: adjusting link_mtu to 1626
Fri May 14 08:50:16 2021 OPTIONS IMPORT: data channel crypto options modified
Fri May 14 08:50:16 2021 Data Channel: using negotiated cipher 'AES-256-GCM'
Fri May 14 08:50:16 2021 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri May 14 08:50:16 2021 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri May 14 08:50:16 2021 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 IFACE=enp3s0 HWADDR=90:2b:34:38:d2:cf
Fri May 14 08:50:16 2021 TUN/TAP device tun0 opened
Fri May 14 08:50:16 2021 TUN/TAP TX queue length set to 100
Fri May 14 08:50:16 2021 /bin/ip link set dev tun0 up mtu 1500
Fri May 14 08:50:16 2021 /bin/ip addr add dev tun0 local 10.10.12.26 peer 10.10.12.25
Fri May 14 08:50:16 2021 /bin/ip route add 192.168.160.0/24 via 10.10.12.25
Fri May 14 08:50:16 2021 /bin/ip route add 10.10.12.0/24 via 10.10.12.25
Fri May 14 08:50:16 2021 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Fri May 14 08:50:16 2021 Initialization Sequence Completed


The proper VPN IP 10.10.12.26 was assigned !


miguel $ nmcli con show
NAME            UUID                                  TYPE      DEVICE  
cabeada893e18de-f470-3eb2-b675-d6deebcad8adethernetenp3s0
tun08e90a55a-aea3-4aac-86f0-9d806a92bfc6tuntun0
UNION           fd54cb50-16e9-4993-b9b3-58f232e4735a  vpn       --      
VPN Apice       97c98842-15ec-4d2a-b9c0-8b2521476282  vpn       --      
VPN apice VIVO  1efdecbd-fcae-477d-bf3a-1e8ff343e417  vpn       --      
miguel $ ip a
1: **lo: **<LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback **00:00:00:00:00:00** brd **00:00:00:00:00:00**
    inet **127.0.0.1**/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 **::1**/128 scope host  
       valid_lft forever preferred_lft forever
2: **enp3s0: **<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state **UP **group default qlen 1000
    link/ether **90:2b:34:38:d2:cf** brd **ff:ff:ff:ff:ff:ff**
    inet **192.168.1.33**/24 brd **192.168.1.255 **scope global dynamic noprefixroute enp3s0
       valid_lft 41604sec preferred_lft 41604sec
    inet6 **fe80::6424:37f8:c78e:d276**/64 scope link noprefixroute  
       valid_lft forever preferred_lft forever
5: **tun0: **<POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100
    link/none  
    inet **10.10.12.26** peer **10.10.12.25**/32 scope global tun0
       valid_lft forever preferred_lft forever
    inet6 **fe80::72b4:d531:1736:2d08**/64 scope link stable-privacy  
       valid_lft forever preferred_lft forever
miguel $ mcli con down 8e90a55a-aea3-4aac-86f0-9d806a92bfc6
Connection 'tun0' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/5)
miguel $ ip a
1: **lo: **<LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback **00:00:00:00:00:00** brd **00:00:00:00:00:00**
    inet **127.0.0.1**/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 **::1**/128 scope host  
       valid_lft forever preferred_lft forever
2: **enp3s0: **<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state **UP **group default qlen 1000
    link/ether **90:2b:34:38:d2:cf** brd **ff:ff:ff:ff:ff:ff**
    inet **192.168.1.33**/24 brd **192.168.1.255 **scope global dynamic noprefixroute enp3s0
       valid_lft 41575sec preferred_lft 41575sec
    inet6 **fe80::6424:37f8:c78e:d276**/64 scope link noprefixroute  
       valid_lft forever preferred_lft forever
5: **tun0: **<POINTOPOINT,MULTICAST,NOARP> mtu 1500 qdisc pfifo_fast state **DOWN **group default qlen 100
    link/none 


So it is not a problem with the VPN itself, but instead, a NM bug/problem that can not handle the OPVN connection anymore, am I right ?

I am far from sure this is a NM bug, the more probable reason is that there are differences between your .ovpn file and what is configured in NM. I am running also NM with OpenVPN on Tumbleweed no problem.

Can you still try the .ovpn file generated by the command I shared earlier? Is that .ovpn file also working on the command prompt?

Yes. Both work on command line. That is why I think it is not a OPVPN “per si” problem.
Also, downgrading the system back to 2021-04-17 , same config file, NM OPVPN works ! The OVPN config file didn´t change between 202021-04-17 2021-04-27, only NM changed.
How can I file a bug against NM ? Do you know where is the proper channel ? May be bugzilla.opensuse.org ? Or there is a more specific place ?

Alternatively, I am trying to donwgrade only the specific Network-manager packages and dependencies, but I was unable to find the previous version

  • (NetworkManager-branding-openSUSE-42.1-3.8.noarch and its dependencies packages)
    Yast/Versions does not show any previous version, reverting to the working snapshot of 2021-04-17 and trying to download the package (zypper in -f NetworkManager-branding-openSUSE=42.1-3.8.noarch) returns No provider of ‘NetworkManager-branding-openSUSE=42.1-3.8’ found.
    There is no previous version of tumbleweed packages on the net ?!?!?!

Yes, given that the .ovpn file generated by the command is working and and older snapshot works I agree that a bug in NM is the most likely.

Network Manager is a standard Linux network configuration tool suite for KDE, gnome and other desktop environments, you can find the repository and issue tracker at https://gitlab.freedesktop.org/NetworkManager/NetworkManager.

Before reporting a bug I would run NM with the log level changed to debug and log trying to connect the VPN.

You can enable on fly fly verbose logging using:

sudo dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:"debug" string:""

en disable it again using:

sudo dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:"info" string:""

That info might give a hint on what is wrong and is anyhow good to have for filing a bug report.