SUMMARY Connection manager does not put the option "autoconnect=true" in the configuration file of nm for a LAN cabled interface when we want an automated connexion of the interface at boot. If we unselect the option "automatic connection with priority", then connection manager removes the "autoconnect-priority=n" and put "autoconnect=false" in the "/etc/NetworkManager/system-connections/LAN.nmconnection" configuration file If we select the option "automatic connection with priority", then connection manager only put "autoconnect-priority=n" but DOES NOT PUT THE REQUIRED "autoconnect=true" in the "/etc/NetworkManager/system-connections/LAN.nmconnection" configuration file It might be the same for ALL interface types supporting the "autoconnect" option. STEPS TO REPRODUCE 1. edit a LAN cabled interface connection 2. unselect then autoconnect option 3. save 4. select then autoconnect option and put priority 98 5. save 6. examine the autoconnect* directive in /etc/NetworkManager/system-connections/LAN.nmconnection OBSERVED RESULT there is no "autoconnect=true" directive in /etc/NetworkManager/system-connections/LAN.nmconnection there is ONLY an "autoconnect-priority=98" directive in this file EXPECTED RESULT there should be an "autoconnect=true" directive in the LAN configuration file otherwise NM will not start this interface at boot. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700T CPU @ 2.90GHz Memory: 15,4 Gio ADDITIONAL INFORMATION root@minipc:~# dpkg -l plasma-nm Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ Nom Version Architecture Description +++-==============-==================================-============-================================= ii plasma-nm 4:5.17.4-0ubuntu1~ubuntu19.10~ppa1 amd64 Plasma5 networkmanager library. root@minipc:~# dpkg -l Display all 61599 possibilities? (y or n) root@minipc:~# dpkg -l network-manager Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ Nom Version Architecture Description +++-===============-===============-============-========================================================= ii network-manager 1.20.4-2ubuntu2 amd64 network management framework (daemon and userspace tools)
I don't think it's an issue, I would assume that autoconnect-priority=X is identical to autoconnect=true && autoconnect-priority=X. Reason is that autoconnect-priority doesn't make any sense with autoconnect disabled. Anyway, it's not us who creates these configuration files, we just send this configuration to NetworkManager, which then creates the configuration files so if there is an issue then you would need to report it to NetworkManager.