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 789626 - auto connect setting is ignored
auto connect setting is ignored
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: general
1.8.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-10-29 17:33 UTC by Scott Palmer
Modified: 2020-11-12 14:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Scott Palmer 2017-10-29 17:33:46 UTC
My onboard Intel network adapter has [X] Connect automatically but when I start my Gnome session, I always have to tell it to Connect which it does without error.

You can't see it in the Gnome dialog windows but this connection is set to also connect to a VPN. I setup this connection with nm-connection-editor.

See also: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725532
Comment 1 Scott Palmer 2017-10-29 17:37:11 UTC
This may be linked to:

https://bugzilla.gnome.org/show_bug.cgi?id=753106
Comment 2 Thomas Haller 2017-10-30 09:27:31 UTC
there is not enough information here.

If the connection is restricted to a particular user (nmcli connection show "$NAME" | grep permission), then make sure that the right user is logged in.

If the device has no carrier, it will not autoconnect.

Most likely the cause is that another connection is already configured on the device. You can see that with `nmcli device` and compare it with `nmcli connection` output.
Comment 3 Scott Palmer 2017-10-31 03:02:09 UTC
$ nmcli connection show
NAME             UUID                                  TYPE            DEVICE          
Houle Security   9cfd06fd-5619-4352-8196-c8cac0136e97  vpn             enp7s4          
Upper            d025899f-7b0d-466c-b76f-76b20456e6ea  802-3-ethernet  enp7s4          
br-2fa2a2e89008  00bc2a01-64f9-446a-826a-338c322d7a9b  bridge          br-2fa2a2e89008 
docker0          3d4e9fa8-65ea-49e5-88c7-b3f7bd70b75e  bridge          docker0         
tun0             7b28fa91-60c7-4400-8651-7e0dead1697a  tun             tun0            
virbr0           ffb23854-0062-4ef5-81eb-7fb5602af661  bridge          virbr0          
vnet0            1bc99a60-7743-41d2-a85a-7dff9c32c3cd  tun             vnet0           
Lower            8002cb46-8354-4cfa-9156-fb27523f7838  802-3-ethernet  --        


$ nmcli device
DEVICE           TYPE      STATE        CONNECTION      
br-2fa2a2e89008  bridge    connected    br-2fa2a2e89008 
docker0          bridge    connected    docker0         
virbr0           bridge    connected    virbr0          
enp7s4           ethernet  connected    Upper           
tun0             tun       connected    tun0            
vnet0            tun       connected    vnet0           
enp2s0           ethernet  unavailable  --              
lo               loopback  unmanaged    --              
virbr0-nic       tun       unmanaged    --    


$ nmcli connection show Upper | grep permission
connection.permissions:                 --
Comment 4 Thomas Haller 2017-10-31 11:26:51 UTC
Are you talking about the connection "Upper" not auto activating?

In the present output, the connection is shown active. What do you expect different there?


Maybe the debug logs would be more helpful. See the notes in https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf for how to provide logfiles.
To get clean logfiles, let's reboot, and let's see why Upper doesn't autoactivate.
Comment 5 André Klapper 2020-11-12 14:26:10 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).