Bug 1526391

Summary: Option "Automatically connect to VPN when using this connection" is missing
Product: [Fedora] Fedora Reporter: Dario Lesca <d.lesca>
Component: gnome-panelAssignee: Orphan Owner <extras-orphan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 27CC: extras-orphan, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 18:47:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Option missing into Gnome Network Panel and Presente in nm-connection-editor none

Description Dario Lesca 2017-12-15 10:59:59 UTC 
Created attachment 1368449 [details]
Option missing into Gnome Network Panel and Presente in nm-connection-editor

Description of problem:
When I setup a network connection, I cannot anymore select what VPN connection start when the connection is used.

Not I must use  "nm-connection-editor" to do that (see attach). 

Version-Release number of selected component (if applicable):
Gnome 3.26.2 - Fedora 27

How reproducible:

Steps to Reproduce:
1. do a new network connection or modify a new connection
2. try set what VPN tunnel start when this connection is used.
3. the option is missing

Actual results:
I cannot setup what VPN tunnel start when a network connection is used

Expected results:
I must setup what VPN tunnel start when a network connection is used


Additional info:
I have add a comment to this Gnome bug:
https://bugzilla.gnome.org/show_bug.cgi?id=672400
Comment 1 Ben Cotton 2018-11-27 17:47:35 UTC 
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 2 Ben Cotton 2018-11-30 18:47:46 UTC 
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.