Before your answer to the above, I am seeing more of this type of error lately. I suspect it's a disconnect between a new updated version of software-updater, netplan, and network-manager. I think is related to these two Bugs (but really needs to be reported as it own bug in software-updater, so that it can be corrected in Main as a priority).
https://bugs.launchpad.net/ubuntu/+s...o/+bug/1789130
https://bugs.launchpad.net/ubuntu/+s...i/+bug/1713803
They are still working on integration of systemd and systemd-networkd. I believe that the last update of software-updater might have had some pointer problems on some systems, which causes a disconnect on pointing to an incorrect network manager renderer. (pointing to a Network Manager that is not defined as being currently in use.
That would explain why it fails seeing a connected network, when it does have a network... And that pressing the "Network Settings" button does "Nothing." It's just confused on what to use as the network manager, and doesn't see correctly that it is really connected.
Netplan started being used in Ubuntu back in 18.04. The Desktops still use Network Manager to add the GUI for network management. If nothing was ever manually configured, when it dynamically renders the network config, the settings in those files may be empty or not. And there seems to be a pointer problem on which network manager is in control as the default network manager renderer.
The above is my assumption based on the fixes that we have been coming up with as work-arounds that seem to solve this problem.
For fixes, it seems if the renderer is manually set to "reestablish" that pointer... It doesn't matter whether that is to NetPlan or to the Network Manager... Then this fixes that problem. Below is the instruction for either:
NetPlan as renderer:
Code:
sudo systemctl stop NetworkManager
sudo systemctl disable NetworkManager
sudo systemctl mask NetworkManager
# Next, start and enable the systemd-networkd service:
sudo systemctl unmask systemd-networkd.service
sudo systemctl enable systemd-networkd.service
sudo systemctl start systemd-networkd.service
# Add the interface configuration to the netplan config file (in the /etc/netplan directory):
#Make a copy of the file
cp /etc/netplan/01-netcfg.yaml ~/Documents/O1-netcfg_old.yaml
# Edit the file with admin privilege's
#### File Contents ###
# This file describes the network interfaces available on your system
# For more information, see netplan(5).network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
### End Contents ###
# Apply the changes by running the following command:
sudo netplan apply
Network Manager as renderer:
Code:
sudo systemctl stop NetworkManager
#Make a copy of the file
cp /etc/netplan/01-netcfg.yaml ~/Documents/O1-netcfg_old.yaml
# Edit the file with admin privilege's
#### File Contents ###
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
# Set and change netplan renderer to NetworkManager GUI tool
network:
version: 2
renderer: NetworkManager
### End contents ###
# start the service back up and apply
sudo systemctl start NetworkManager
sudo netplan apply
Note that after doing that to explicitly use the Network Manager as the renderer, that it's easiest to use the GUI Network Manager > Settings to set the settings in the GUI and save to generate the new network settings files.
There's 100's of ways to do similar things, but those two fixes seem to work.
Bookmarks