Bug 1406992 - On Centos-7 (updated to 7.3) existing openconnect VPN works, but NM won't let me edit it, or add another like it.
Summary: On Centos-7 (updated to 7.3) existing openconnect VPN works, but NM won't let...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: NetworkManager-openconnect
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-22 02:44 UTC by fred smith
Modified: 2017-04-19 13:49 UTC (History)
5 users (show)

Fixed In Version: NetworkManager-openconnect-1.2.4-4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-19 13:49:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
debug-output-edit-openconnect-vpn.log (6.24 KB, text/plain)
2017-02-23 20:13 UTC, fred smith
no flags Details

Description fred smith 2016-12-22 02:44:02 UTC
Description of problem:
Can neither edit an existing openconnect VPN, nor add a new one.

Version-Release number of selected component (if applicable):
NetworkManager-openconnect-0.9.8.6-2.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.upgrade a 7.2 system that already has existing (working) openconnect vpn configured
2.attempt to edit that existing vpn, OR attempt to add a new openconnect vpn.
3.

Actual results:
attempting to add one gives a list of vpn types that DOES NOT contain openconnect.

attempting to edit an existing one gives a text box containing:
Could not edit connection
Could not find vpn plugin for 'org.freedesktop.networkmanager.openconnect'

Expected results:
ability to add or edit an openconnect vpn

Additional info:
rpm -qa | grep -i networkman
NetworkManager-team-1.4.0-13.el7_3.x86_64
NetworkManager-openconnect-0.9.8.6-2.el7.x86_64
NetworkManager-bluetooth-1.4.0-13.el7_3.x86_64
NetworkManager-glib-devel-1.4.0-13.el7_3.x86_64
NetworkManager-libnm-1.4.0-13.el7_3.x86_64
NetworkManager-libreswan-1.2.4-1.el7.x86_64
NetworkManager-openvpn-1.0.8-1.el7.x86_64
NetworkManager-pptp-1.1.0-3.20150428git695d4f2.el7.x86_64
NetworkManager-tui-1.4.0-13.el7_3.x86_64
NetworkManager-glib-1.4.0-13.el7_3.x86_64
NetworkManager-vpnc-gnome-1.0.8-1.el7.x86_64
NetworkManager-1.4.0-13.el7_3.x86_64
NetworkManager-openvpn-gnome-1.0.8-1.el7.x86_64
NetworkManager-libnm-devel-1.4.0-13.el7_3.x86_64
NetworkManager-wwan-1.4.0-13.el7_3.x86_64
NetworkManager-adsl-1.4.0-13.el7_3.x86_64
NetworkManager-vpnc-1.0.8-1.el7.x86_64
NetworkManager-wifi-1.4.0-13.el7_3.x86_64

rpm -qa | grep -i opencon
NetworkManager-openconnect-0.9.8.6-2.el7.x86_64
openconnect-7.06-1.el7.x86_64

cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)

It behaves exactly the same on my EL7 desktop and my EL7 netbook, both being up to date Centos-7 systems.

Comment 1 Thomas Haller 2016-12-22 09:42:29 UTC
NetworkManager-openconnect contains a GTK plugin that is used by nm-connection-editor.

For version 0.9.8.6-2, the plugin links against libnm-glib/libnm-util.
In CentOS 7.3, nm-connection-editor instead links against libnm.

libnm-glib/libnm-util libraries are incompatible with libnm.

The solution is to upgrade the plugin to a newer version. The newer versions provides a plugin for both libnm-glib/libnm-util and libnm based GUIs.

(another workaround would be to downgrade nm-connection-editor)

You can also edit the connection using nmcli (though that is quite inconvenient).
I think, nmcli is also able to ask for openconnect passwords via `nmcli --ask --show-password connection up "$VPN"`).


TL;DR:
need to build Fedora 25's NetworkManager-openconnect package for EPEL.
(beware to use >= 1.2.4-3 to avoid the package-split bug 1398425)

Comment 2 fred smith 2016-12-22 22:13:06 UTC
On Thu, Dec 22, 2016 at 09:42:29AM +0000, bugzilla wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1406992
>
>
>
> --- Comment #1 from Thomas Haller <thaller> ---
> NetworkManager-openconnect contains a GTK plugin that is used by
> nm-connection-editor.
>
> For version 0.9.8.6-2, the plugin links against libnm-glib/libnm-util.
> In CentOS 7.3, nm-connection-editor instead links against libnm.
>
> libnm-glib/libnm-util libraries are incompatible with libnm.
>
> The solution is to upgrade the plugin to a newer version. The newer versions

which item is this? NetworkManager-openconnect, or NM-connection-editor?
Or both?
> provides a plugin for both libnm-glib/libnm-util and libnm based GUIs.
>
> (another workaround would be to downgrade nm-connection-editor)
>
> You can also edit the connection using nmcli (though that is quite
> inconvenient).
> I think, nmcli is also able to ask for openconnect passwords via `nmcli --ask
> --show-password connection up "$VPN"`).
>
>
> TL;DR:
> need to build Fedora 25's NetworkManager-openconnect package for EPEL.
> (beware to use >= 1.2.4-3 to avoid the package-split bug 1398425)

I've done a mock build of NetworkManager-openconnect using 1.2.4-3 (from
Fedora testing) and it installs, but now I get errors about not finding
NM-connection-editor.

So, do I need to rebuild that, too?

Comment 3 Thomas Haller 2016-12-22 22:31:44 UTC
you need to upgrade NetworkManager-openconnect package (the VPN plugin).
For example to version >= 1.2.4-3 as is in Fedora 25.

It's unclear which error you are getting about nm-c-e(??). You shouldn't need anything else there. nm-c-e (from network-manager-applet package) should be a recent enough version on CentOS7.3 and work fine...

Comment 4 fred smith 2016-12-23 01:04:30 UTC
yes, I did build NetworkManager-openconnect 1.2.4-3, on Centos-7 as I said in comment 2. it seemed to build cleanly, and installed without trouble.

after that, is what I described at the end of Comment 2.

having installed that, I not only get the error stated above, I also cannot connect to the existing openconnect vpn.

hence, I ask do I also need to build a newer nm-connection-editor?

Comment 5 Thomas Haller 2016-12-26 21:11:03 UTC
as said, I would not expect you need to update nm-connection-editor.
If it still isn't working with an updated nm-openconnect plugin, there isn't enough information to say way.

Comment 6 fred smith 2016-12-26 23:49:48 UTC
I reverted to the original NM-openconnect since it, at least, allows me to connect to my office, unlike the new one.

Can you (or anyone else) suggest things I could test or try that might provide useful information for diagnosing/fixing it?

Comment 7 fred smith 2017-02-15 19:20:08 UTC
just wondering... is anybody working on this?

is there any hope of a fix before RHEL/CentOS-8 ?

thanks!

Comment 8 Murilo Opsfelder Araujo 2017-02-23 00:32:44 UTC
Hi, Thomas.

Is it possible that you or David kindly rebase NetworkManager-openconnect to the same version in f25 branch of fedpkg?

Assuming CentOS packages are identical to RHEL ones, this bug might also be affecting RHEL Workstation users, isn't it?

Comment 9 fred smith 2017-02-23 02:49:32 UTC
Murilo, as I mentioned above, I did a build on Centos-7 of the NM-openconnect from F25, and while it builds and installs, it encounters another problem I don't know how to solve.

I keep hoping someone who works on NM-openconnect, and who has some idea of all the interactions between various packages/tools, might jump in here and solve it for us.

I'm not completely dead in the water, because the (single) pre-existing openconnect vpn I had set up (prior to the Centos 7.3 upgrade) still works.
but I can't edit it, and can't create new ones. Unfortunately, many businesses insist on using Cisco's anyconnect SSL vpn, so I need openconnect so I can connect to them.

Comment 10 Murilo Opsfelder Araujo 2017-02-23 17:49:23 UTC
Fred,

I think the next step here would be collecting some NetworkManager debugging logs hoping that that will give us a clue of what's going on with NM, openconnect plugin, and connection editor.

The https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/examples/shell/nm-logging.sh may help, for example:

$ sudo ./nm-logging.sh debug
$ journalctl -f -u NetworkManager

Then try to edit your openconnect vpn profile.

Comment 11 fred smith 2017-02-23 20:13:35 UTC
Created attachment 1257017 [details]
debug-output-edit-openconnect-vpn.log

this is NM debug output from an attempt to edit an openconnect vpn that pre-existed the upgrade from Centos 7.2 to 7.3.

Note that the attempt failed with on-screen dialog as described in the original bug report.

I don't see anything informative in this log, but maybe someone else will.

Comment 12 fred smith 2017-02-23 20:20:16 UTC
note that attempting to ADD a new openconnect vpn doesn't work either, again as described in the original report.

the debug output attached in comment 11 actually occurs immediately when (1) right-click the NM panel icon, then (2) click either edit, or add. the output seems to be the same either way.

there is no further debug output when editing or adding. You can't actually get into an edit program, or the list of VPN types to add doesn't include openconnect.

Comment 13 Murilo Opsfelder Araujo 2017-02-24 00:52:43 UTC
If you call `/usr/bin/nm-connection-editor` on terminal, does it open?

Are all dynamic dependencies of nm-connection-editor satisfied?

$ ldd /usr/bin/nm-connection-editor

Comment 14 fred smith 2017-02-24 01:25:55 UTC
Murilo: 

yes it does. however, I get a dialog saying "could not find VPN plugin for 'org.freedesktop.NetworkManager.openconnect'.

yum reports that the NetworkManager-openconnect package is installed:

yum list installed | grep -i openconnect
NetworkManager-openconnect.x86_64     0.9.8.6-2.el7                  installed  
openconnect.x86_64                    7.06-1.el7                     @epel

NetworkManager-openconnect.x86_64 package contains:

rpm -ql NetworkManager-openconnect.x86_64
/etc/NetworkManager/VPN/nm-openconnect-service.name
/etc/dbus-1/system.d/nm-openconnect-service.conf
/usr/lib64/NetworkManager/libnm-openconnect-properties.so
/usr/libexec/nm-openconnect-auth-dialog
/usr/libexec/nm-openconnect-service
/usr/libexec/nm-openconnect-service-openconnect-helper
/usr/share/doc/NetworkManager-openconnect-0.9.8.6
/usr/share/doc/NetworkManager-openconnect-0.9.8.6/AUTHORS
/usr/share/doc/NetworkManager-openconnect-0.9.8.6/COPYING
/usr/share/doc/NetworkManager-openconnect-0.9.8.6/ChangeLog
/usr/share/gnome-vpn-properties/openconnect
/usr/share/gnome-vpn-properties/openconnect/nm-openconnect-dialog.ui
/usr/share/locale/as/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/bg/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/bn_IN/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ca/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ca@valencia/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/cs/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/da/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/de/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/el/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/en_GB/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/eo/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/es/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/et/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/eu/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/fa/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/fr/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/gl/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/gu/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/he/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/hu/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/id/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/it/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/kn/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ko/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/lt/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/lv/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/mr/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/nb/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/nl/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/or/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/pa/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/pl/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/pt/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/pt_BR/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ro/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ru/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/sl/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/sr/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/sr@latin/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/sv/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ta/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/te/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/tr/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ug/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/uk/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/vi/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/zh_CN/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/zh_HK/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/zh_TW/LC_MESSAGES/NetworkManager-openconnect.mo

there is also openconnect-7.06-1.el7.x86_64, which contains:

rpm -ql NetworkManager-openconnect.x86_64
/etc/NetworkManager/VPN/nm-openconnect-service.name
/etc/dbus-1/system.d/nm-openconnect-service.conf
/usr/lib64/NetworkManager/libnm-openconnect-properties.so
/usr/libexec/nm-openconnect-auth-dialog
/usr/libexec/nm-openconnect-service
/usr/libexec/nm-openconnect-service-openconnect-helper
/usr/share/doc/NetworkManager-openconnect-0.9.8.6
/usr/share/doc/NetworkManager-openconnect-0.9.8.6/AUTHORS
/usr/share/doc/NetworkManager-openconnect-0.9.8.6/COPYING
/usr/share/doc/NetworkManager-openconnect-0.9.8.6/ChangeLog
/usr/share/gnome-vpn-properties/openconnect
/usr/share/gnome-vpn-properties/openconnect/nm-openconnect-dialog.ui
/usr/share/locale/as/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/bg/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/bn_IN/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ca/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ca@valencia/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/cs/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/da/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/de/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/el/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/en_GB/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/eo/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/es/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/et/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/eu/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/fa/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/fr/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/gl/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/gu/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/he/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/hu/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/id/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/it/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/kn/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ko/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/lt/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/lv/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/mr/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/nb/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/nl/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/or/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/pa/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/pl/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/pt/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/pt_BR/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ro/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ru/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/sl/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/sr/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/sr@latin/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/sv/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ta/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/te/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/tr/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/ug/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/uk/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/vi/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/zh_CN/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/zh_HK/LC_MESSAGES/NetworkManager-openconnect.mo
/usr/share/locale/zh_TW/LC_MESSAGES/NetworkManager-openconnect.mo

Comment 15 fred smith 2017-02-24 03:33:58 UTC
re whether ldd shows any unsatisifed requirements, I don't see any. here is the output:

ldd /usr/bin/nm-connection-editor
	linux-vdso.so.1 =>  (0x00007ffd75dfc000)
	libnma.so.0 => /lib64/libnma.so.0 (0x00007f11542bc000)
	libgudev-1.0.so.0 => /lib64/libgudev-1.0.so.0 (0x00007f11542ac000)
	libgtk-3.so.0 => /lib64/libgtk-3.so.0 (0x00007f11539f4000)
	libgdk-3.so.0 => /lib64/libgdk-3.so.0 (0x00007f115375c000)
	libatk-1.0.so.0 => /lib64/libatk-1.0.so.0 (0x00007f1153534000)
	libpangocairo-1.0.so.0 => /lib64/libpangocairo-1.0.so.0 (0x00007f1153324000)
	libgdk_pixbuf-2.0.so.0 => /lib64/libgdk_pixbuf-2.0.so.0 (0x00007f11530fc000)
	libcairo-gobject.so.2 => /lib64/libcairo-gobject.so.2 (0x00007f1152eec000)
	libpango-1.0.so.0 => /lib64/libpango-1.0.so.0 (0x00007f1152c9c000)
	libcairo.so.2 => /lib64/libcairo.so.2 (0x00007f1152974000)
	libnm.so.0 => /lib64/libnm.so.0 (0x00007f115268c000)
	libgio-2.0.so.0 => /lib64/libgio-2.0.so.0 (0x00007f115230c000)
	libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007f11520bc000)
	libgmodule-2.0.so.0 => /lib64/libgmodule-2.0.so.0 (0x00007f1151eb4000)
	libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f1151b7c000)
	libjansson.so.4 => /lib64/libjansson.so.4 (0x00007f115196c000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f1151664000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f115144c000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f115122c000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f1150e64000)
	libudev.so.1 => /lib64/libudev.so.1 (0x00007f1150e4c000)
	librt.so.1 => /lib64/librt.so.1 (0x00007f1150c44000)
	libcap.so.2 => /lib64/libcap.so.2 (0x00007f1150a3c000)
	libdw.so.1 => /lib64/libdw.so.1 (0x00007f11507f4000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f11505ec000)
	libX11.so.6 => /lib64/libX11.so.6 (0x00007f11502ac000)
	libXi.so.6 => /lib64/libXi.so.6 (0x00007f115009c000)
	libXfixes.so.3 => /lib64/libXfixes.so.3 (0x00007f114fe94000)
	libatk-bridge-2.0.so.0 => /lib64/libatk-bridge-2.0.so.0 (0x00007f114fc64000)
	libpangoft2-1.0.so.0 => /lib64/libpangoft2-1.0.so.0 (0x00007f114fa4c000)
	libfontconfig.so.1 => /lib64/libfontconfig.so.1 (0x00007f114f80c000)
	libXinerama.so.1 => /lib64/libXinerama.so.1 (0x00007f114f604000)
	libXrandr.so.2 => /lib64/libXrandr.so.2 (0x00007f114f3f4000)
	libXcursor.so.1 => /lib64/libXcursor.so.1 (0x00007f114f1e4000)
	libXcomposite.so.1 => /lib64/libXcomposite.so.1 (0x00007f114efdc000)
	libXdamage.so.1 => /lib64/libXdamage.so.1 (0x00007f114edd4000)
	libXext.so.6 => /lib64/libXext.so.6 (0x00007f114ebbc000)
	libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007f114e9b4000)
	libharfbuzz.so.0 => /lib64/libharfbuzz.so.0 (0x00007f114e754000)
	libfreetype.so.6 => /lib64/libfreetype.so.6 (0x00007f114e4ac000)
	libpng15.so.15 => /lib64/libpng15.so.15 (0x00007f114e27c000)
	libpixman-1.so.0 => /lib64/libpixman-1.so.0 (0x00007f114dfcc000)
	libEGL.so.1 => /usr/lib64/nvidia/libEGL.so.1 (0x00007f114ddc4000)
	libxcb-shm.so.0 => /lib64/libxcb-shm.so.0 (0x00007f114dbbc000)
	libxcb-render.so.0 => /lib64/libxcb-render.so.0 (0x00007f114d9ac000)
	libxcb.so.1 => /lib64/libxcb.so.1 (0x00007f114d784000)
	libXrender.so.1 => /lib64/libXrender.so.1 (0x00007f114d574000)
	libz.so.1 => /lib64/libz.so.1 (0x00007f114d35c000)
	libGL.so.1 => /usr/lib64/nvidia/libGL.so.1 (0x00007f114d01c000)
	libssl3.so => /lib64/libssl3.so (0x00007f114cdd4000)
	libsmime3.so => /lib64/libsmime3.so (0x00007f114cbac000)
	libnss3.so => /lib64/libnss3.so (0x00007f114c884000)
	libnssutil3.so => /lib64/libnssutil3.so (0x00007f114c654000)
	libplds4.so => /lib64/libplds4.so (0x00007f114c44c000)
	libplc4.so => /lib64/libplc4.so (0x00007f114c244000)
	libnspr4.so => /lib64/libnspr4.so (0x00007f114c004000)
	libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f114bdfc000)
	libffi.so.6 => /lib64/libffi.so.6 (0x00007f114bbf4000)
	libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f114b9cc000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f114b7ac000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f1154524000)
	libattr.so.1 => /lib64/libattr.so.1 (0x00007f114b5a4000)
	libelf.so.1 => /lib64/libelf.so.1 (0x00007f114b38c000)
	liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f114b164000)
	libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f114af54000)
	libatspi.so.0 => /lib64/libatspi.so.0 (0x00007f114ad24000)
	libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x00007f114aadc000)
	libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f114a8ac000)
	libgraphite2.so.3 => /lib64/libgraphite2.so.3 (0x00007f114a67c000)
	libGLdispatch.so.0 => /usr/lib64/nvidia/libGLdispatch.so.0 (0x00007f114a38c000)
	libXau.so.6 => /lib64/libXau.so.6 (0x00007f114a184000)
	libnvidia-tls.so.367.57 => /usr/lib64/nvidia/tls/libnvidia-tls.so.367.57 (0x00007f1149f7c000)
	libnvidia-glcore.so.367.57 => /usr/lib64/nvidia/libnvidia-glcore.so.367.57 (0x00007f114823c000)
	libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f1147fd4000)

Comment 16 Fedora Update System 2017-02-24 12:56:13 UTC
NetworkManager-openconnect-1.2.4-4.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-3a86e33517

Comment 17 fred smith 2017-02-24 23:55:24 UTC
I just installed the new rpm from testing NetworkManager-openconnect-1.2.4-4.el7, and NetworkManager-openconnect-gnome, and it looks like the problem(s) I reported are solved:
1. I can create a new openconnect vpn and use it
2. I can edit an existing one
3. the pre-existing one still works.

thanks!

Comment 18 Fedora Update System 2017-02-25 03:17:43 UTC
NetworkManager-openconnect-1.2.4-4.el7 has been pushed to the Fedora EPEL 7 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-EPEL-2017-3a86e33517

Comment 19 Murilo Opsfelder Araujo 2017-03-01 19:36:05 UTC
(In reply to Fedora Update System from comment #16)
> NetworkManager-openconnect-1.2.4-4.el7 has been submitted as an update to
> Fedora EPEL 7.
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-3a86e33517

Thank you Thomas!

Comment 20 Fedora Update System 2017-04-19 13:49:44 UTC
NetworkManager-openconnect-1.2.4-4.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.


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