Bug 32888

 $ urpmq --requires plasma-applet-nm-fortisslvpnui | grep open
networkmanager-openconnect
 $ urpmq --whatrequires networkmanager-openconnect | grep fortisslvpnui
plasma-applet-nm-fortisslvpnui

Yes, 'plasma-applet-nm-fortisslvpnui' does indeed require 'networkmanager-openconnect'; and inversely, 'plasma-applet-nm-fortisslvpnui' is required by 'networkmanager-openconnect'.

But where do you find:
> Package [plasma-applet-nm-fortisslvpnui] should [depend on] openfortivpn and
networkmanager-openfortivpn
?

CC: (none) => lewyssmith

When i want to establish a VPN connection which i configured using PLasma Network Manager Applet i get the message Networkmanager is missing support for fortisslvpn. I have the same setup on Ubuntu and there it works, no access to that Ubuntu Machine at the Moment, will post packages of that System when having access again. looks like the Network-Manager Plugin involved is https://github.com/NetworkManager/NetworkManager-fortisslvpn

Fixed on Cauldron with next plasma-nm-5.93.0-2.mga10 update!

CC: (none) => geiger.david68210

Fixed for mga9 also with plasma-nm-5.27.10-1.1.mga9 in Core/Updates_testing!

So I also fixed plasma-applet-nm-ssh which requires now networkmanager-ssh.

Assigning to QA,

Packages in 9/Core/Updates_testing:
======================
plasma-applet-nm-5.27.10-1.2.mga9
plasma-applet-nm-fortisslvpnui-5.27.10-1.2.mga9
plasma-applet-nm-l2tp-5.27.10-1.2.mga9
plasma-applet-nm-libreswan-5.27.10-1.2.mga9
plasma-applet-nm-openconnect-5.27.10-1.2.mga9
plasma-applet-nm-openvpn-5.27.10-1.2.mga9
plasma-applet-nm-pptp-5.27.10-1.2.mga9
plasma-applet-nm-ssh-5.27.10-1.2.mga9
plasma-applet-nm-strongswan-5.27.10-1.2.mga9
plasma-applet-nm-vpnc-5.27.10-1.2.mga9

openfortivpn-1.21.0-1.mga9
networkmanager-fortisslvpn-1.4.0-3.mga9
networkmanager-fortisslvpn-gnome-1.4.0-3.mga9
networkmanager-ssh-1.2.12-1.mga9
networkmanager-ssh-gnome-1.2.12-1.mga9

From SRPMS:
plasma-nm-5.27.10-1.2.mga9.src.rpm
networkmanager-ssh-1.2.12-1.mga9.src.rpm
networkmanager-fortisslvpn-1.4.0-3.mga9.src.rpm
openfortivpn-1.21.0-1.mga9.src.rpm

Assignee: bugsquad => qa-bugs

MGA9-64 Plasma. I use Network Manager on this system so as to use it with openvpn. Consequently, I have had plasma-applet-nm and plasma-applet-nm-openvpn installed, but not the rest.

No installation issues with updating the packages already installed. I activated an existing Surfshark vpn, and it worked as designed. Then I added another Surfshark server to the list already set up, and that one worked, too.

I went to MCC and installed all of the NM Plasma vpn applets. Then I brought up the Connections page in System Settings, and browsed through the new choices for vpn types, settling on opening the configuration pages for both of the Fortinet options that now appeared. Both opened and I guess they looked normal. That's as far as I can go, so I backed out and shut the window.

CC: (none) => andrewsfarm

(In reply to Thomas Andrews from comment #6)
> MGA9-64 Plasma. I use Network Manager on this system so as to use it with
> openvpn. Consequently, I have had plasma-applet-nm and
> plasma-applet-nm-openvpn installed, but not the rest.
> 
> No installation issues with updating the packages already installed. I
> activated an existing Surfshark vpn, and it worked as designed. Then I added
> another Surfshark server to the list already set up, and that one worked,
> too.
> 
> I went to MCC and installed all of the NM Plasma vpn applets. Then I brought
> up the Connections page in System Settings, and browsed through the new
> choices for vpn types, settling on opening the configuration pages for both
> of the Fortinet options that now appeared. Both opened and I guess they
> looked normal. That's as far as I can go, so I backed out and shut the
> window.

I can confirm it works, i just updated the package by enabling the core updates testing repo temporary.

(In reply to Mike Burgener from comment #7)
> I can confirm it works, i just updated the package by enabling the core
> updates testing repo temporary.

Thank you for the test

(In reply to katnatek from comment #8)
> (In reply to Mike Burgener from comment #7)
> > I can confirm it works, i just updated the package by enabling the core
> > updates testing repo temporary.
> 
> Thank you for the test

Yes, that is what I was waiting for. Validating.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

DavidG deserves a big thanks for taking this on board with his usual alactrity, and fixing it. It was not trivial.

CC: lewyssmith => (none)

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2024-0084.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED