Description of problem: I had a Fedora 24 workstation in which I had a VPN configured in Network Manager using openconnect. I upgraded to Fedora 25, and, after that, I wasn't able to connect to the VPN, nor edit its data. The following message was showing in system log: NetworkManager[17300]: <error> [1480008191.6833] vpn-connection[<...>]: Failed to request VPN secrets #3: No agents were availab After installing NetworkManager-openconnect-gnome package and rebooting the machine (strangely restarting NetworkManager service didn't make things work for me --- edit was working, but connecting was not), everything worked fine. I suppose this package would need to be installed anyway if someone has NetworkManager-openconnect installed and GNOME, as it was my case. Version-Release number of selected component (if applicable): NetworkManager-openconnect-1.2.3-0.20160606git5009f9.fc25.x86_64 NetworkManager-openconnect-gnome-1.2.3-0.20160606git5009f9.fc25.x86_64 Actual results: VPN could not connect and not editable. Expected results: VPN can connect and can be edited.
there are two problems: - NetworkManager-openconnect-gnome is not part of the default installation for many fedora spins, though it should: https://bugzilla.redhat.com/show_bug.cgi?id=1398739#c6 - The package-split change of NetworkManager-openconnect and NetworkManager-openconnect-gnome does not properly contain Obsoletes, to ensure that the gnome-subpackage is installed on update: https://bugzilla.redhat.com/show_bug.cgi?id=1398561#c1
*** Bug 1398561 has been marked as a duplicate of this bug. ***
*** Bug 1398739 has been marked as a duplicate of this bug. ***
*** Bug 1400577 has been marked as a duplicate of this bug. ***
(In reply to Thomas Haller from comment #1) > there are two problems: > > - NetworkManager-openconnect-gnome is not part of the default installation > for many fedora spins, though it should: > https://bugzilla.redhat.com/show_bug.cgi?id=1398739#c6 for that, we have bug 1384223. > - The package-split change of NetworkManager-openconnect and > NetworkManager-openconnect-gnome does not properly contain Obsoletes, to > ensure that the gnome-subpackage is installed on update: > https://bugzilla.redhat.com/show_bug.cgi?id=1398561#c1 actually, the package split seems to be correct using "Obsoletes". It seems that the package is not installed on update due to dnf bug 1261034. I let this BZ depend on bug 1261034. -- note that the longer this is broken, the less it makes point to fix it, because all users will have upgraded in the meantime.
> Obsoletes: NetworkManager-openconnect < 1.2.3-0 Reporter had 1.2.3-0.git....., so it is higher that 1.2.3-0. Moreover, you will need to add same obsoletes into the main package.
> Reporter had 1.2.3-0.git....., so it is higher that 1.2.3-0. That's after the update though. F24 has only 1.2.2 (unless you're using the Kannolo Copr).
(In reply to Kevin Kofler from comment #7) > > Reporter had 1.2.3-0.git....., so it is higher that 1.2.3-0. > > That's after the update though. F24 has only 1.2.2 (unless you're using the > Kannolo Copr). This is correct. 1.2.3-0 was the version after the update to Fedora 25.
I just upgraded to F25 and ran into this problem but installing NetworkManager-openconnect-gnome did not fix the problem for me. Since I am using the KDE spin (not Kannolo), it would seem that the fix is Gnome-specific. Is there a solution for KDE to this problem? Noe that I can edit the VPN connection but I can't connect and get the "Failed to request VPN secrets" message.
NetworkManager-openconnect-1.2.4-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ba7028b69c
NetworkManager-openconnect-1.2.4-3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ba7028b69c
Reposting from Bodhi: This did not fix #1398425 for me: I still had to manually do: dnf install --enablerepo=updates-testing NetworkManager-openconnect-gnome From reading the bug, I assumed installing NetworkManager-openconnect was supposed to pull in -gnome automatically. Perhaps I misunderstood? Or maybe I just didn't read the linked "dnf" bug.
NetworkManager-openconnect was split in two packages: NetworkManager-openconnect and NetworkManager-openconnect-gnome. The latter depends on the former. Certainly NetworkManager-openconnect is not supposed to install NetworkManager-openconnect-gnome, because then the package split would be pointless. What is supposed to work, if you have NetworkManager-openconnect-1.2.2-1.fc24 installed (the last version before the split), when you *upgrade* you should end up with NetworkManager-openconnect and NetworkManager-openconnect-gnome. That should be fixed with version 1.2.4-3. That is: an upgrade from <=1.2.2-1 to >=1.2.4-3 should install the gnome subpackage. What is not fixed is when you incrementally upgrade from 1.2.2-1.fc24 -> 1.2.4-1.fc25 -> 1.2.4-3.fc25, then you end up without gnome subpackage. That is, users that are already hit by this bug, have to manually install the sub package.
Im installed fresh Cinnamon F25, and was unable to setup VPN without NetworkManager-openconnect-gnome So problem affects fresh installs too.
(In reply to Kirill Berezin from comment #14) > Im installed fresh Cinnamon F25, and was unable to setup VPN without > NetworkManager-openconnect-gnome > > So problem affects fresh installs too. see comment 5.
> Certainly NetworkManager-openconnect is not supposed to install NetworkManager-openconnect-gnome, because then the package split would be pointless. Thank you for clarifying.
NetworkManager-openconnect-1.2.4-3.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
I've upgraded from f24 to f25 as well, and the problem persists. I have all the necessary packages installed: NetworkManager-openconnect-gnome-1.2.4-3.fc25.x86_64 openconnect-7.08-1.fc25.x86_64 NetworkManager-openconnect-1.2.4-3.fc25.x86_64 The problem is: Once I try to add a VPN connection of type 'OpenVPN', the 'Add' button stays grayed out, although I filled in all the necessary information. Any ideas? This worked without problems in f24.
your problem is clearly unrelated to this bug. if you want to add an OpenVPN connection, the openconnect packages do not matter.
I just upgraded from Fedora 24 on 2016-12-28 and ended up without NetworkManager-openconnect-gnome. (In case it matters, I used https://fedoraproject.org/wiki/Upgrading_Fedora_using_package_manager because I'm running Fedora under Qubes OS and fedup didn't work the last time I tried it. I used dnf-1.1.10-1.fc24, and the log shows that NetworkManager-openconnect-1.2.2-1.fc24.x86_64 was upgraded to 1.2.4-3.fc25.x86_64 without installing NetworkManager-openconnect-gnome.) It's confusing to have this bug marked as fixed. If the underlying problem is indeed bug 1261034 and nothing else needs to be done specific to NetworkManager-openconnect-gnome, please reopen the bug and make it a duplicate of bug 1261034.
(In reply to Matt McCutchen from comment #20) From the information provided, I don't know why it wouldn't work, or whether bug 1261034 is the cause. It worked for me testing with a local repository and `dnf upgrade NetworkManager-openconnect`.
I've posted a reduced version of my original Fedora 24 RPM database that triggered the bug (~4 MB): https://mattmccutchen.net/private/rh-bug-1398425-repro.tar.bz2 If I extract this and run "dnf --disablerepo='*' --enablerepo=fedora --enablerepo=updates --installroot=$PWD --releasever=25 distro-sync", dnf proposes to upgrade NetworkManager-openconnect without installing NetworkManager-openconnect-gnome. This is using dnf-1.1.10-4.fc25 and the dnf configuration from my outer Fedora 25 system against the current state of the Fedora 25 repositories. Despite the uncontrolled variables, hopefully this will be enough for anyone interested to reproduce the problem in the near future.
*** Bug 1435959 has been marked as a duplicate of this bug. ***
As per Comment 13, I think this can be closed. Its CANTFIX if one first upgrades to 1.2.4-1.fc25 (and manual intervention if required). Its NOTABUG if you upgrade *past* 1.2.4-1.fc25