SUMMARY I've installed plasma-nm with OpenConnect support. Also openconnect and networkmanager-openconnect are installed. However, when I try to add an OpenConnect VPN, the option is not present in the list. I've tried rebooting, but that doesn't work. In the system logs, searching for plasma-nm or openconnect, nothing is found. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2
I can create and use openconnect VPNs with Gnome's nm-applet. The defined vpn then appears in the list of plasma-nm's defined connections. When trying to run it, I get a notification that the VPN plugin is missing. In the logs I see some repetitions of (order varies) plasmashell[18243]: file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:196:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... } plasmashell[18243]: file:///usr/lib64/qt5/qml/org/kde/plasma/components/TabButton.qml:69:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... } plasmashell[18243]: file:///usr/lib64/qt5/qml/org/kde/plasma/components/Highlight.qml:34:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... } and then plasmashell[18243]: plasma-nm: VPN "org.freedesktop.NetworkManager.openconnect" not found, skipping When trying to edit the defined vpn, there are only the General Setup and IPv4 tabs.
I've got `libopenconnect5` as the only openconnect package installed on KDE Neon User Edition (5.20.3 Plasma) and I can see the option to create a Cisco AnyConnect Compatible VPN (openconnect) in the Connections settings. Are you able to test on 5.20.3 (if I understand correctly it's in the gentoo ebuild testing section)?
(In reply to Justin Zobel from comment #2) > I've got `libopenconnect5` as the only openconnect package installed on KDE > Neon User Edition (5.20.3 Plasma) and I can see the option to create a Cisco > AnyConnect Compatible VPN (openconnect) in the Connections settings. OK, that is a first confirmation that it should work. I guess there's an issue on Gentoo. > Are you able to test on 5.20.3 (if I understand correctly it's in the gentoo > ebuild testing section)? No. I'm not going to move my daily driver to testing packages. This bug was carried over from 5.18 to 5.19 and when looking at the plasma-nm repository, I've not seen any relevant commits since a while.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
New information was added with comment 3; changing status for inspection.
You need NetworkManager-openconnect plugin.
(In reply to Jan Grulich from comment #6) > You need NetworkManager-openconnect plugin. I do. Please read the original bug description. Also, please see Comment 1, which shows that networkmanager-openconnect works (using Gnome's nm-applet).
Then it's not a runtime issue, but you are probably missing openconnect headers and libraries during the build. You should see that in the log after you run CMake command, it will report if the OpenConnect plugin will be build.
(In reply to Jan Grulich from comment #8) > Then it's not a runtime issue, but you are probably missing openconnect > headers and libraries during the build. You should see that in the log after > you run CMake command, it will report if the OpenConnect plugin will be > build. It seems all libraries and plugins are built (see lines suffixed with ******; some uninteresting lines cut …): $ tree -f /usr | grep openconnect │ ├── /usr/include/openconnect.h │ │ │ ├── /usr/lib/NetworkManager/VPN/nm-openconnect-service.name │ │ ├── /usr/lib64/NetworkManager/libnm-vpn-plugin-openconnect-editor.so ****** │ │ ├── /usr/lib64/NetworkManager/libnm-vpn-plugin-openconnect.so ****** │ ├── /usr/lib64/libopenconnect.so -> libopenconnect.so.5.6.0 ****** │ ├── /usr/lib64/libopenconnect.so.5 -> libopenconnect.so.5.6.0 ****** │ ├── /usr/lib64/libopenconnect.so.5.6.0 ****** │ │ ├── /usr/lib64/pkgconfig/openconnect.pc │ │ │ ├── /usr/lib64/qt5/plugins/libplasmanetworkmanagement_openconnectui.so ****** │ ├── /usr/libexec/nm-openconnect-auth-dialog │ ├── /usr/libexec/nm-openconnect-service │ ├── /usr/libexec/nm-openconnect-service-openconnect-helper │ ├── /usr/libexec/openconnect │ │ ├── /usr/libexec/openconnect/csd-post.sh │ │ ├── /usr/libexec/openconnect/csd-wrapper.sh │ │ ├── /usr/libexec/openconnect/hipreport-android.sh │ │ ├── /usr/libexec/openconnect/hipreport.sh │ │ └── /usr/libexec/openconnect/tncc-wrapper.py │ ├── /usr/sbin/openconnect │ │ ├── /usr/share/appdata/network-manager-openconnect.metainfo.xml │ │ ├── /usr/share/doc/networkmanager-openconnect-1.2.6 │ │ │ ├── … │ │ ├── /usr/share/doc/openconnect-8.09-r3 │ │ │ ├── … │ │ └── /usr/share/gnome-vpn-properties/openconnect │ │ └── /usr/share/gnome-vpn-properties/openconnect/nm-openconnect-dialog.ui │ │ ├── /usr/share/kservices5/plasmanetworkmanagement_openconnect_globalprotectui.desktop ****** │ │ ├── /usr/share/kservices5/plasmanetworkmanagement_openconnect_juniperui.desktop ****** │ │ ├── /usr/share/kservices5/plasmanetworkmanagement_openconnectui.desktop ****** │ │ │ │ ├── … │ │ │ │ ├── /usr/share/locale/en_GB/LC_MESSAGES/openconnect.mo │ │ │ │ ├── /usr/share/locale/en_US/LC_MESSAGES/openconnect.mo │ │ │ │ ├── /usr/share/locale/es/LC_MESSAGES/openconnect.mo │ │ │ ├── … │ │ │ │ ├── /usr/share/locale/lt/LC_MESSAGES/openconnect.mo │ │ │ │ ├── /usr/share/locale/nl/LC_MESSAGES/NetworkManager-openconnect.mo │ │ │ │ ├── /usr/share/locale/nl/LC_MESSAGES/openconnect.mo │ │ │ │ ├── /usr/share/locale/nl/LC_MESSAGES/plasmanetworkmanagement_openconnectui.mo │ │ │ │ ├── /usr/share/locale/pa/LC_MESSAGES/openconnect.mo │ │ │ │ ├── … │ │ │ ├── /usr/share/man/man8/openconnect.8.bz2 The build logs also do not show any errors or differences between openconnect and the other VPN types. I know that other Gentoo users have managed to configure openconnect vpns using plasma-nm, so it must be something quite specific. What and how to find out is therefore the question.
That all looks good. I have no idea why you don't see OpenConnect in the list. Do you see other VPN types? Btw. OpenConnect is not named as "OpenConnect", it is named "CiscoAnyConnect Compatibile VPN".
(In reply to Jan Grulich from comment #10) > That all looks good. I have no idea why you don't see OpenConnect in the > list. Do you see other VPN types? Yes. OpenVPN and vpnc configured and working, also FortiSSL in the past. The connection defined by nm-applet is also selectable (shows VPN-plug-in: openconnect), but trying to activate it gives the behavior described in Comment 1. > Btw. OpenConnect is not named as "OpenConnect", it is named "CiscoAnyConnect > Compatibile VPN". Not present either.
It turns out that this problem was caused by the fact that (for some unknown reason) my cache directory was owned by root and not the user. This resulted in kbuildsycoca5 not being able to run, which apparently caused all kinds of small issues like this until recently, when with a frameworks update applications couldn't be found, kparts weren't found, etc.