Bug 1384223 - Not opened Cisco AnyConnect Compatible VPN (openconnect) editor
Summary: Not opened Cisco AnyConnect Compatible VPN (openconnect) editor
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: comps
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stephen Gallagher
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-12 20:54 UTC by Mikhail
Modified: 2017-12-12 11:02 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 11:02:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot with error message (18.93 KB, image/png)
2016-10-12 20:54 UTC, Mikhail
no flags Details

Description Mikhail 2016-10-12 20:54:55 UTC
Created attachment 1209772 [details]
screenshot with error message

Description of problem:
Not opened Cisco AnyConnect Compatible VPN (openconnect) editor
Show instead error message: "unable to load VPN connection editor"

$ rpm -q NetworkManager-openconnect 
NetworkManager-openconnect-1.2.3-0.20160606git5009f9.fc25.x86_64

Comment 1 Thomas Haller 2016-10-12 21:35:04 UTC
did you install NetworkManager-openconnect-gnome?

Comment 2 Mikhail 2016-10-13 03:38:03 UTC
My mistake. In Fedora 24 this package was installed out of box.

Comment 3 David Woodhouse 2016-10-13 08:35:30 UTC
Yeah, and it still should be. Is 'comps' still the right place to assign that?

Comment 4 Kevin Fenzi 2016-10-13 15:10:54 UTC
I can look at this at some point, but if you all want things done quicker, please submit a pull request against https://pagure.io/fedora-comps with the changes. 

I guess NetworkManager split out some more subpackages here?

Comment 5 David Woodhouse 2016-10-13 16:37:23 UTC
Right. Aside from fixing comps we should probably also do virtual Provides: for the UIs and PackageKit integration to bring them in as required, like we do for codecs etc.

Comment 6 Kevin Fenzi 2016-10-20 19:23:35 UTC
I was going to look at making a PR here, but I am not sure what is actually wanted. 

All the NetworkManager*gnome subpackages in Workstation? Or in all the desktops?

Perhaps we should make a new NetworkManager-gui group and just include that in the others?

Adding lkundrak here for any NM comment...

Comment 7 David Woodhouse 2016-10-20 19:51:17 UTC
I think the idea is that for all VPN types, if Fedora 24 pulled in NetworkManager-$VPNTYPE by default then Fedora 25 should have NetworkManager-$VPNTYPE-gnome. Except perhaps the KDE spins, which would have the equivalent plasma-nm-$VPNTYPE package instead.

But virtual Provides: and pulling them in on demand would also be useful...

Comment 8 Eric Work 2016-12-09 03:13:19 UTC
I just ran into this problem after an upgrade from Fedora 24 to Fedora 25.  From what I'm reading the NetworkManager-openconnect-gnome package didn't exist in Fedora 24 and it's functionality was part of NetworkManager-openconnect?  If so I guess that explains why it didn't get installed as part of the upgrade.  Any idea when this will get resolved?  I already worked around the issue by installing NetworkManager-openconnect-gnome so I'm not waiting around for a resolution at least for this bug.

Comment 9 Thomas Haller 2016-12-09 10:02:08 UTC
(In reply to Eric Work from comment #8)
> I just ran into this problem after an upgrade from Fedora 24 to Fedora 25. 
> From what I'm reading the NetworkManager-openconnect-gnome package didn't
> exist in Fedora 24 and it's functionality was part of
> NetworkManager-openconnect?  If so I guess that explains why it didn't get
> installed as part of the upgrade.  Any idea when this will get resolved?  I
> already worked around the issue by installing
> NetworkManager-openconnect-gnome so I'm not waiting around for a resolution
> at least for this bug.

this BZ is about which packages are installed by default. Your issue is on update. See bug 1398425

Comment 10 Thomas Haller 2016-12-09 10:09:16 UTC
see also: https://pagure.io/fedora-comps/pull-request/69

Comment 11 Rajneesh Gadge 2017-05-14 08:03:40 UTC
This would not work out of the box with Fedora 25, but you may try running it as /opt/cisco/anyconnect/bin/vpnui and it will throw the real error

Mine was stuck with error "error while loading shared libraries: libpangox-1.0.so.0" I tried "dnf install pangox-compat" which fixed the launch issue and I'm able to successfully connect to the VPN.

Comment 12 Fedora End Of Life 2017-11-16 18:42:30 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 13 Fedora End Of Life 2017-12-12 11:02:30 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.