Created attachment 1482329 [details] Screen shot VPN gui Description of problem: Unable to set 'Connect automatically' in VPN gui dialogue Version-Release number of selected component (if applicable): $ NetworkManager --version 1.10.10-1.fc28 How reproducible: Always Steps to Reproduce: 1. Configure VPN 2. Seek 'Connect automatically' toggle 3. Actual results: No 'Connect automatically' toggle Expected results: 'Connect automatically' toggle Additional info: A recent example of NetworkManager VPN gui with this facility and check-box can be found here: https://p6.zdassets.com/hc/theme_assets/287093/200032898/Fedora05.png (the referring page says Updated: April 16, 2018 12:56 https://support.hidemyass.com/hc/en-us/articles/202721566-HMA-Pro-VPN-on-Fedora-IPSec-OpenVPN-) Compare attached screen shot of the present VPN config gui
> A recent example of NetworkManager VPN gui with this facility and check-box can > be found here: > https://p6.zdassets.com/hc/theme_assets/287093/200032898/Fedora05.png "Connect automatically" maps to the "connection.autoconnect" property (which is documented in `man nm-settings`). Setting this to TRUE has no effect for VPN profiles (at the moment), because NetworkManager daemon does not support it for VPNs. It was correctly removed from gnome-control-center at https://bugzilla.gnome.org/show_bug.cgi?id=792365 . Not because the feature wouldn't be useful, but because it cannot work until NetworkManager daemon supports it. I re-purpose this bug for adding the feature to NetworkManager (which must happen first). Upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=753106 An alternative solution to the problem is setting the VPN profile as a "connection.secondaries" of another non-VPN profile. nm-connection-editor calls that "Automatically connect to VPN when using this connection".
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.