Bug 1327858 - Gnome GUI makes impossible to add any StrongSwan VPN
Summary: Gnome GUI makes impossible to add any StrongSwan VPN
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager-strongswan
Version: 23
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Pavel Šimerda (pavlix)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-16 23:55 UTC by Bernardo Donadio
Modified: 2016-10-27 03:21 UTC (History)
3 users (show)

Fixed In Version: NetworkManager-strongswan-1.3.1-1.fc23.1 NetworkManager-strongswan-1.4.0-2.fc24
Clone Of:
Environment:
Last Closed: 2016-09-28 14:50:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot of the GUI issue (40.04 KB, image/png)
2016-04-16 23:55 UTC, Bernardo Donadio
no flags Details

Description Bernardo Donadio 2016-04-16 23:55:28 UTC
Created attachment 1148029 [details]
Screenshot of the GUI issue

Description of problem:
The NetworkManager-strongswan-gnome GUI is broken, without primordial fields being rendered, making the addition of any StrongSwan VPN impossible. No other field than the Name and Firewall Zone are being rendered on screen.


Version-Release number of selected component (if applicable):
NetworkManger-strongswan-gnome-1.3.1-1.fc23.x86_64

How reproducible:
I have been able to reproduce on 2 different completely updated Fedora 23 systems.

Steps to Reproduce:
1. Install NetworkManager-strongswan-gnome package.
2. Open Network settings on Gnome control panel.
3. Click to add a New connection (the plus sign)
4. Select the "VPN option", then the "IPsec/IKEv2 (strongswan)".

Actual results:
The dialog is rendered without important fields, like the gateway to connect, the user, password ou certificate information. Also, it´s impossible to ever click the "Add" button, since it's greyed out.
There a screenshot attached to this bug report with the result.

Expected results:
It's expected to be able to fill the basic connection information trough the GUI for StrongSwan.

Additional info:

Comment 1 Blueowl 2016-08-09 19:38:03 UTC
You can use nm-connection-editor that displays strongswan properties correctly.

gnome-control-center uses gtk_box_pack_start() function that failed due to incorrect strongswan UI file, preventing the panel from showing widgets. However, the problem has been fixed upstream:
https://git.strongswan.org/?p=strongswan.git;a=commit;h=3889db0d9dcaca1f2927cb996a2f66a528fadc17

You can copy the UI file [1] to /usr/share/gnome-vpn-properties/strongswan/nm-strongswan=dialog.ui as a temporary fix.

[1] https://git.strongswan.org/?p=strongswan.git;a=blob_plain;f=src/frontends/gnome/properties/nm-strongswan-dialog.ui;hb=refs/heads/nm-1.2

Comment 2 Bernardo Donadio 2016-08-31 18:20:33 UTC
Hi Blueowl.

The following procedure resulted in error while opening said dialog (Error: unable to load VPN connection editor).
----
sudo cp /usr/share/gnome-vpn-properties/strongswan/nm-strongswan-dialog.ui{,.bkp}
sudo wget -O /usr/share/gnome-vpn-properties/strongswan/nm-strongswan-dialog.ui https://git.strongswan.org/?p=strongswan.git;a=blob_plain;f=src/frontends/gnome/properties/nm-strongswan-dialog.ui;hb=refs/heads/nm-1.2
----

Also, the following error is displayed in the journal:
----
gnome-control-center.desktop[25011]: ** (gnome-control-center:25011): WARNING **: Couldn't load builder file: (unknown)
gnome-control-center.desktop[25011]: (gnome-control-center:25011): GLib-GObject-WARNING **: invalid (NULL) pointer instance
gnome-control-center.desktop[25011]: (gnome-control-center:25011): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
----

Is there anything more that I should do?

Meanwhile, indeed, the old nm-connection-editor indeed works as expected (only with the old ui file, using the one you provided causes nm-connection-editor also to fail).

Thanks!

Comment 4 Bernardo Donadio 2016-09-18 02:31:47 UTC
Blueowl, the issue was actually the download command being wrong. Now, everything works!

Any chance this being fixed in F24?

Thanks.

Comment 5 Fedora Update System 2016-09-23 06:52:43 UTC
NetworkManager-strongswan-1.3.1-1.fc23.1 has been pushed to the Fedora 23 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-43494300d1

Comment 6 Fedora Update System 2016-09-23 08:00:48 UTC
NetworkManager-strongswan-1.4.0-1.fc24 has been pushed to the Fedora 24 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-3600786766

Comment 7 Fedora Admin XMLRPC Client 2016-09-27 13:39:19 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 8 Fedora Update System 2016-09-28 05:58:30 UTC
NetworkManager-strongswan-1.4.0-2.fc24 has been pushed to the Fedora 24 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-3600786766

Comment 9 Bernardo Donadio 2016-09-28 14:50:45 UTC
NetworkManager-strongswan-1.4.0-2.fc24 fixes the issue for me.

Comment 10 Fedora Update System 2016-10-05 08:50:38 UTC
NetworkManager-strongswan-1.3.1-1.fc23.1 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2016-10-27 03:21:16 UTC
NetworkManager-strongswan-1.4.0-2.fc24 has been pushed to the Fedora 24 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.