After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 792365 - Don't show "connection.autoconnect" option for VPN's in gnome-control-center
Don't show "connection.autoconnect" option for VPN's in gnome-control-center
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Network
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-01-09 12:17 UTC by Richard
Modified: 2018-03-02 11:56 UTC
See Also:
GNOME target: ---
GNOME version: 3.25/3.26


Attachments
network: Don't show "Auto-connect" for VPNs (2.76 KB, patch)
2018-02-10 13:14 UTC, Bastien Nocera
committed Details | Review

Description Richard 2018-01-09 12:17:51 UTC
After coming back from suspension my openvpn doesn't connect automatically as configured to connect automatically.
Tested on Ubuntu gnome 17.10 amd64.
Comment 1 Thomas Haller 2018-01-09 12:38:09 UTC
There is not enough information provided to understand what happens.

In general, connection.autoconnect=yes does not work for VPNs.
You might want to try to set "connection.secondaries" on an underlying connection.
Comment 2 Richard 2018-01-09 13:09:06 UTC
I remember that on a older stack and older distro it worked fine setting it all up by UI, now it seems that a lot of UI settings have been removed. I will try your advice and edit the network profile manually.
Comment 3 Richard 2018-01-09 16:09:27 UTC
Ok, editing the file manually solved the problem but what should we do about this bug? Change component to indicate the UI?
Comment 4 Thomas Haller 2018-01-10 09:51:51 UTC
can you describe better what you are doing, and what you think is the bug here?
Comment 5 Richard 2018-01-10 10:47:25 UTC
The bug is that automatic connection in the VPN properties GUI is selected and it doesn't work, and as I said this all worked in an earlier gnome stack using the GUI only, it appears options have been removed from the GUI.
Comment 6 Thomas Haller 2018-01-10 10:59:19 UTC
In nm-connection-editor, I don't see such an option for VPNs. It's unclear which GUI you are using, do you use gnome-control-center from Gnome 3? Which version of the GUI?

Besides, I think that NetworkManager until now never supported autoconnect for VPNs. It's a missing feature. If the GUI exposed such a setting, was it really working with NetworkManager?
Comment 7 Richard 2018-01-10 11:09:37 UTC
nm-connection-editor doesn't show that option, it's in the gnome-control-center where it shows, i'm using version 3.26.2

I think the setting exposed in a prior gnome-control-center was a connection.secondaries on a primary network to connect also a secondary.

Should I change this bug as to gnome-control-center ?
Comment 8 Thomas Haller 2018-01-10 12:53:24 UTC
g-c-e shouldn't have a "connection.autoconnect" option for VPN's, because it doesn't work. Also, the "connection.secondary" should possibly be shown for non VPN types.

Reassigning.
Comment 9 Bastien Nocera 2018-02-10 13:14:30 UTC
Created attachment 368208 [details] [review]
network: Don't show "Auto-connect" for VPNs

It's not supported for VPNs.
Comment 10 Bastien Nocera 2018-02-16 12:28:19 UTC
Attachment 368208 [details] pushed as 9b9e0e0 - network: Don't show "Auto-connect" for VPNs
Comment 11 Richard 2018-02-17 16:59:18 UTC
Does this fix implement connection.secondary for non VPN's?
Comment 12 Bastien Nocera 2018-03-02 11:56:55 UTC
(In reply to effew from comment #11)
> Does this fix implement connection.secondary for non VPN's?

No, it does not.