After upgrading to networkmanager-1.4.0-r1 and networkmanager-openvpn-1.2.4 (from 1.0.12-r1 and 1.0.8 resp), now when I connect to my VPN the plasma-nm applet doesn't show the correct icon (with the padlock) all the time. Reproducible: Always
Does a rebuild of kde-frameworks/networkmanager-qt help? If not, please try rebuilding kde-plasma/plasma-nm next.
Hey Andreas, I forgot to mention that, I rebuild both plasma-nm and networkmanager-qt, then logged out/in with the problem persisting. Here's another odd observation: My wifi connection is a "system" configuration, while my openVPN is a "user" configuration. Prior to the upgrade, when I would log out of my account wth the VPN connected, it would automatically disconnect the VPN and leave the wifi connected. Now it doesn't disconnect from VPN, and when I log back in, the icon is correct (has the padlock). This may indicate two bugs, but it also may be related.
I just tried networkmanager-1.4.2 which _just_ entered the tree. Same result.
I tried upgrading kde-frameworks/* to 5.26 from stable (5.23), and rebuild networkmanager-qt and plasma-nm, but to no avail. Next I upgraded kde-plasma/* to 5.7.5, and now it works as expected. Not sure if the kde-frameworks was a necessary step, but it's installed.
I take that back, it _worked_ once, now it is exhibiting same + worse behaviour. Sometimes the icon just stays in the unconnected state, even with just wifi connected. Other times, it shows the VPN connected, but no wifi connection (just VPN and no others). I'm not sure what else to test, aside from going back to stable frameworks, stable plasma, and masking the new networkmanager + networkmanager-openvpn.
No need to downgrade Plasma+Frameworks, this is ultimately caused by the networkmanager upgrade.
As per IRC, I tried upgrading to kde-frameworks/networkmanager-qt/5.26.0-r1. It seems to have fixed the normal WiFi connection status/icons in the systray. However on another machine which also uses networkmanager-openvpn, VPN connections are still messed up. When I connect to the VPN, it doesn't show the padlock icon to indicate VPN connected, and also a spurious tun0 adapter shows up in my connection list (it did not do this on previous versions). If I then logout/login with VPN connected, the icon is correct, but if I disconnect/reconnect to the VPN it doesn't indicate the connection with the padlock. Is there a similar patch for networkmanager-openvpn? I'm currently using networkmanager-1.4.0-r1 and networkmanager-openvpn-1.2.4 with kde-frameworks/networkmanager-qt/5.26.0-r1.
According to KDE upstream, the root cause of this is actually in networkmanager itself, with networkmanager-qt-5.26.0-r1 just backporting attempts to work around the breakage. The GNOME bug has links to networkmanager patches you could try. Also CCing gnome team in case they know which networkmanager release might contain these patches, or if they know anything further about the breakage eg. the networkmanager-openvpn issue.
There's a patch in networkmanager-qt.git master that is vpn state related, you could try that, but it seems based on the parent commit. However, the same line was existing already, so you could un-comment it by example: https://quickgit.kde.org/?p=networkmanager-qt.git&a=commit&h=e9f2cedefa98d2d58caeb30b1c3099144c4fbbba
NM-1.4.2 includes the patches... could you give it a try?
@Pacho I don't see any difference between NM-1.4.0 and NM-1.4.2 wrt the openvpn bad behaviour.
The fix from NM side is included in 1.4.2: https://bugzilla.gnome.org/show_bug.cgi?id=770629#c6
Is it now fixed using latest stable kde-frameworks/networkmanager-qt-5.26.0-r2?
Yes it seems to be changing at least the states that I put it through. Thanks a lot for the friendly support :)
Thanks for reporting.
