| 2019-12-05 15:38:18 |
Owen Savill |
bug |
|
|
added bug |
| 2019-12-05 16:41:35 |
Kai-Heng Feng |
bug task added |
|
linux (Ubuntu) |
|
| 2019-12-05 17:00:17 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2019-12-10 10:16:17 |
Owen Savill |
tags |
amd64 apport-bug focal third-party-packages |
amd64 apport-bug apport-collected focal third-party-packages |
|
| 2019-12-10 10:16:19 |
Owen Savill |
description |
Ubuntu 20.04
network-manager:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
*** 1.20.4-2ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
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:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
*** 1.20.4-2ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
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
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu13
Architecture: amd64
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2017-12-06 (734 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
NonfreeKernelModules: nvidia_modeset nvidia
Package: network-manager 1.20.4-2ubuntu3
PackageArchitecture: amd64
Tags: focal
Uname: Linux 5.4.2-050402-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
_MarkForUpload: True |
|
| 2019-12-10 10:16:19 |
Owen Savill |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/1855297/+attachment/5311413/+files/Dependencies.txt |
|
| 2019-12-10 10:16:21 |
Owen Savill |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1855297/+attachment/5311414/+files/ProcCpuinfoMinimal.txt |
|
| 2019-12-10 10:16:23 |
Owen Savill |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1855297/+attachment/5311415/+files/ProcEnviron.txt |
|
| 2019-12-10 10:19:05 |
Owen Savill |
description |
Ubuntu 20.04
network-manager:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
*** 1.20.4-2ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
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
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu13
Architecture: amd64
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2017-12-06 (734 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
NonfreeKernelModules: nvidia_modeset nvidia
Package: network-manager 1.20.4-2ubuntu3
PackageArchitecture: amd64
Tags: focal
Uname: Linux 5.4.2-050402-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
_MarkForUpload: True |
Ubuntu 20.04
network-manager:
Installed: 1.20.4-2ubuntu2
Candidate: 1.20.4-2ubuntu2
Version table:
*** 1.20.4-2ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
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
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu13
Architecture: amd64
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2017-12-06 (734 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
NonfreeKernelModules: nvidia_modeset nvidia
Package: network-manager 1.20.4-2ubuntu3
PackageArchitecture: amd64
Tags: focal
Uname: Linux 5.4.2-050402-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu13
Architecture: amd64
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2017-12-06 (734 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
NonfreeKernelModules: nvidia_modeset nvidia
Package: network-manager 1.20.4-2ubuntu3
PackageArchitecture: amd64
Tags: focal
Uname: Linux 5.4.2-050402-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
_MarkForUpload: True |
|
| 2019-12-10 10:19:05 |
Owen Savill |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/1855297/+attachment/5311416/+files/Dependencies.txt |
|
| 2019-12-10 10:19:07 |
Owen Savill |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1855297/+attachment/5311417/+files/ProcCpuinfoMinimal.txt |
|
| 2019-12-10 10:19:09 |
Owen Savill |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1855297/+attachment/5311418/+files/ProcEnviron.txt |
|
| 2019-12-10 10:29:02 |
Owen |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2019-12-10 10:29:40 |
Owen |
network-manager (Ubuntu): status |
New |
Confirmed |
|
