Bug 1472076 - nm-connection-editor can't read it's own exported configuration
Summary: nm-connection-editor can't read it's own exported configuration
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: network-manager-applet
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-18 03:47 UTC by Bill Nottingham
Modified: 2018-05-29 12:09 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:09:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
the config (248 bytes, text/plain)
2017-07-18 03:49 UTC, Bill Nottingham
no flags Details

Description Bill Nottingham 2017-07-18 03:47:48 UTC
Description of problem:

SSIA.

Version-Release number of selected component (if applicable):

1.8.2-2.fc26

How reproducible:

100%

Steps to Reproduce:
1. take machine with working openvpn NM configuration
2. export it with nm-connection editor
3. attempt to import that exported configuration

Actual results:

The file "whatever you called it" could not be read or does not contain recognized VPN connection information.

Error: Key file contains line "client" which is not a key-value pair, group, or comment.

Expected results:

Works

Additional info:

Comment 1 Bill Nottingham 2017-07-18 03:49:01 UTC
Created attachment 1300221 [details]
the config

Comment 2 Beniamino Galvani 2017-07-21 13:06:35 UTC
Which NetworkManager-openvpn and NetworkManager-openvpn-gnome versions do you have? That file is imported without problems here with:

NetworkManager-openvpn-1.2.10-1.fc26.x86_64
NetworkManager-openvpn-gnome-1.2.10-1.fc26.x86_64

Comment 3 Bill Nottingham 2017-07-21 14:09:48 UTC
NetworkManager-openvpn-1.2.10-1.fc26.x86_64
NetworkManager-openvpn-gnome-1.2.10-1.fc26.x86_64

here as well.

Comment 4 Fedora End Of Life 2018-05-03 08:45:00 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 5 Fedora End Of Life 2018-05-29 12:09:07 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.