After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around.
Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again.
I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed.
Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.20.4-2ubuntu2
Uname: Linux 5.4.2-050402-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Dec 5 15:24:51 2019
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-12-06 (729 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.20.4 connected started full enabled enabled enabled enabled enabled
Ubuntu 20.04
network-manager: gb.archive. ubuntu. com/ubuntu focal/main amd64 Packages dpkg/status
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
*** 1.20.4-2ubuntu2 500
500 http://
100 /var/lib/
After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around.
Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again.
I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed.
Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected.
ProblemType: Bug generic x86_64 dules: nvidia_modeset nvidia
DistroRelease: Ubuntu 20.04
Package: network-manager 1.20.4-2ubuntu2
Uname: Linux 5.4.2-050402-
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Dec 5 15:24:51 2019
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-12-06 (729 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.20.4 connected started full enabled enabled enabled enabled enabled