| Summary: | kde-plasma/plasma-nm-5.19.5: openconnect integration not working | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Erik Quaeghebeur <gentoo> |
| Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=426058 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build log plasma-nm | ||
|
Description
Erik Quaeghebeur
2020-09-03 09:55:51 UTC
Created attachment 658090 [details]
build log plasma-nm
It works fine for me with net-vpn/openvpn installed, but I'm by no means an expert with VPNs. (In reply to Andreas Sturmlechner from comment #2) > It works fine for me with net-vpn/openvpn installed, […]. This is OpenConnect-specific. I have many other VPNs of different types that work perfectly with plasma-nm. Please test with 5.19.5, which is going to be the upcoming stable version. (In reply to Andreas Sturmlechner from comment #4) > Please test with 5.19.5, which is going to be the upcoming stable version. OK, I'll wait until stabilization to test. The effort to mark and deal with unstable is not worth it, given that I have a workaround. In the mean time, if anyone is interested, they can test whether with 5.18 (5.19) they see OpenConnect VPN as a config option when they install plasma-nm with the openconnect use flag. (In reply to Erik Quaeghebeur from comment #5) > (In reply to Andreas Sturmlechner from comment #4) > > Please test with 5.19.5, which is going to be the upcoming stable version. > OK, I'll wait until stabilization to test. The effort to mark and deal with > unstable is not worth it, given that I have a workaround. Basically, two files: https://gitweb.gentoo.org/proj/kde.git/tree/Documentation/package.accept_keywords/kde-frameworks-5.73.keywords https://gitweb.gentoo.org/proj/kde.git/tree/Documentation/package.accept_keywords/kde-plasma-5.19.keywords (In reply to Andreas Sturmlechner from comment #6) > (In reply to Erik Quaeghebeur from comment #5) > > (In reply to Andreas Sturmlechner from comment #4) > > > Please test with 5.19.5, which is going to be the upcoming stable version. > > OK, I'll wait until stabilization to test. The effort to mark and deal with > > unstable is not worth it, given that I have a workaround. > > Basically, two files: > […] I appreciate providing the files to make it easy. Even so, I'm in a job transition and cannot take an increased risk of disturbance on my daily driver laptop. I'm now on 5.19.5 and the problem still exists. From the logs: 08.10.2020 11:53:18:158 plasmashell plasma-nm: VPN "org.freedesktop.NetworkManager.openconnect" not found, skipping I have kde-plasma/plasma-nm-5.19.5[openconnect] installed and my dependencies seem to be fine: $ equery d openconnect * These packages depend on openconnect: kde-plasma/plasma-nm-5.19.5 (openconnect ? net-vpn/openconnect) net-vpn/networkmanager-openconnect-1.2.6 (>=net-vpn/openconnect-3.02) $ equery d networkmanager-openconnect * These packages depend on networkmanager-openconnect: kde-plasma/plasma-nm-5.19.5 (openconnect ? net-vpn/networkmanager-openconnect) To test this issue for yourself, I do not think you need to even try to establish an openconnect VPN. OpenConnect is not even listed in the list of VPN options for me. (I defined it using the Gnome nm-applet and then it appears also in plasma-nm, but without all tabs present and without being functional.) I would be really grateful if someone could install plasma-nm with the openconnect use flag and check on their end whether they then have an option to define an openconnect VPN or not. That way, I know whether this is a general problem, or specific to my setup. I was able to get it mostly working on my system. I was able to create a VPN connection and get most of the way through the connection process. The connection did fail to connect in the end, but I think that may be due to a policykit failure related to dbus-broker. (In reply to Mike Gilbert from comment #10) > I was able to get it mostly working on my system. I was able to create a VPN > connection and get most of the way through the connection process. Thanks very much for doing the effort of testing this. Tour positive result means that something is wrong/different on my system. What is the best way to find out what? > $ USE=openconnect emerge -1v plasma-nm ...was enough for me to get the openconnect option shown. I do not have gnome-extra/nm-applet installed. > [ebuild R ] net-vpn/openconnect-8.10-r1:0/5::gentoo USE="gnutls nls -doc -gssapi -libproxy -lz4 -smartcard -stoken -test" > [ebuild R ] net-vpn/networkmanager-openconnect-1.2.6::gentoo USE="-gtk" > [ebuild R ] net-misc/networkmanager-1.26.6::gentoo USE="bluetooth elogind introspection modemmanager ncurses nss (policykit) ppp wext wifi -audit -connection-sharing -dhclient -dhcpcd -gnutls -iwd -json -ofono -ovs -resolvconf (-selinux) -systemd -teamd -test -vala" > [ebuild R ] dev-qt/qtnetwork-5.15.2:5/5.15::gentoo USE="networkmanager ssl -bindist -connman -debug -gssapi -libproxy -libressl -sctp -test" > [ebuild R ] kde-plasma/plasma-nm-5.20.4 USE="openconnect -debug -modemmanager -teamd -test" (In reply to Andreas Sturmlechner from comment #12) > > $ USE=openconnect emerge -1v plasma-nm > ...was enough for me to get the openconnect option shown. I do not have > gnome-extra/nm-applet installed. Thanks a lot for trying. There are some difference in use flags, but nothing that seems related. There are slight differences in minor version, but given Mike's report, it seems unlikely that is the cause. What on my system is the culprit is still a mystery. However, it seems appropriate that you close this as WORKSFORME. (I'll be installing a new system in the new year. I hope it works there as that'll give me a comparison point.) I'll close it for now, do reopen if you have any new findings. |
