Current build uses gtk+3, whereas gnome-control centers uses gtk4+. As a result, vpn connection editor isn't available. Rebuilding against gtk+4 is enough to fix the issue.
Summary: rebuild with gtk4+ needed => networkmanager-openconnect: rebuild with gtk4+ neededSource RPM: networkmanager-openconnect => networkmanager-openconnect-1.2.8-3.mga9.src.rpm
Please test networkmanager-openconnect-1.2.8-3.1.mga9.x86_64.rpm Packages in 9/Core/Updates_testing: ====================== networkmanager-openconnect-1.2.8-3.1.mga9 From SRPMS: networkmanager-openconnect-1.2.8-3.1.mga9.src.rpm
CC: (none) => geiger.david68210Assignee: bugsquad => qa-bugs
Version: Cauldron => 9
(In reply to David GEIGER from comment #1) > Please test networkmanager-openconnect-1.2.8-3.1.mga9.x86_64.rpm > > Packages in 9/Core/Updates_testing: > ====================== > networkmanager-openconnect-1.2.8-3.1.mga9 > > From SRPMS: > networkmanager-openconnect-1.2.8-3.1.mga9.src.rpm Added advisory to SVN, with subject: Updated networkmanager-openconnect re-adds VPN connection editor And description: The VPN connection editor was unavailable, because networkmanager-openconnect was built with gtk+3. This update is built with gtk+4, thus fixing the issue. Please remove the "advisory" keyword if the advisory needs to be changed.
Keywords: (none) => advisorySummary: networkmanager-openconnect: rebuild with gtk4+ needed => networkmanager-openconnect: rebuild with gtk4+ needed for the VPN connection editorCC: (none) => marja11
Sorry this took this long. I was mistaken on what was required to test this. I created a MGA9-64 Gnome install in VirtualBox, enabled Network Manager, and started it. Then I went to "Settings" and attempted to add a Cisco-compatible VPN, but the VPN connection editor was unavailable, confirming the issue. Then I used qarepo to update networkmanager-openconnect, and tried again. Still no editor available. Rebooted, just to see if it made a difference. It didn't. Sorry Marja, but I'm removing the advisory keyword, as something still isn't working.
CC: (none) => andrewsfarmKeywords: advisory => (none)
(In reply to Thomas Andrews from comment #3) > Sorry this took this long. I was mistaken on what was required to test this. > > I created a MGA9-64 Gnome install in VirtualBox, enabled Network Manager, > and started it. Then I went to "Settings" and attempted to add a > Cisco-compatible VPN, but the VPN connection editor was unavailable, > confirming the issue. > > Then I used qarepo to update networkmanager-openconnect, and tried again. > Still no editor available. Rebooted, just to see if it made a difference. It > didn't. > > Sorry Marja, but I'm removing the advisory keyword, as something still isn't > working. Thanks for having removed it :-) Adding the feedback keyword
Keywords: (none) => feedback
Nothing has changed. While the update installs cleanly, it does not fix the issue. Removing the feedback keyword, and assigning this bug back to bugsquad.
Keywords: feedback => (none)Assignee: qa-bugs => bugsquad
Re-assigning back to DavidG who did the requested re-build. Sorry David...
Assignee: bugsquad => geiger.david68210
Assigning to QA, Packages in 9/Core/updates_testing: ====================== networkmanager-openconnect-1.2.10-1.mga9 networkmanager-openvpn-1.10.2-1.mga9 networkmanager-vpnc-1.2.8-1.1.mga9 From SRPMS: networkmanager-openconnect-1.2.10-1.mga9.src.rpm networkmanager-openvpn-1.10.2-1.mga9.src.rpm networkmanager-vpnc-1.2.8-1.1.mga9.src.rpm
Assignee: geiger.david68210 => qa-bugs
Source RPM: networkmanager-openconnect-1.2.8-3.mga9.src.rpm => networkmanager-openconnect, networkmanager-openvpn, networkmanager-vpnc
Advisory in SVN has been updated with the SRPMs from comment 7
Keywords: (none) => advisory
Fired up my Gnome guest once more, and repeated the test of comment 3. This time the openconnect editor opened. Since I don't have access to a VPN provider that uses openconnect, that's as far as I went with this test. However, since networkmanager-openvpn is now also being updated, I will be testing that separately with my Surfshark account. I will try it in Gnome, but as I'm unfamiliar with setting up a vpn in that DE, I will also test in Plasma on real hardware.
Ah, I see what happened now. When I tested in comment 3, I tried to bring up the vpnc editor, not the openconnect one. That didn't actually test the update it was supposed to be testing, but it did point out that at least one of the other protocol editors must have needed to be rebuilt as well. So I guess making a mistake was a good thing, after all. Anyway, I already had a Surfshark vpn set up on my HP Pavilion 15 MGA9-64 Plasma system. I made sure it was shut off, and updated the three packages from comment 7. Then I used the "import" function to load vpn information for a new server in a different location, and used the editor to input the username and password that had been supplied by surfshark. I started the new vpn, and suddenly my IP looked like I was in a different US city. Then I started my Gnome guest anew, and worked my way through the process of importing the information for yet another server location, used the editor to add username and password, and successfully connected. It all looks good to me. Giving it an OK, and validating.
Keywords: (none) => validated_updateWhiteboard: (none) => MGA9-64-OKCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2023-0132.html
Status: NEW => RESOLVEDResolution: (none) => FIXED