[Touch-packages] [Bug 1860985] Re: packagekitd using 100% CPU
So now running at about 33% CPU. It was a broken update PPA. Really! Exactly how many times a second are the PPAs being checked for updates?! It's a broken PPA, surely the package manager can handle a broken PPA better than 100% CPU usage. And exactly what is it doing that requires 20% CPU usage when it's idle?! Is there an admin program for this? I think it only needs to update a couple of times a day. The only admin I've found offers very few options as to the frequency of update checking and none of them seem to work. It slows down boot, even though this should be disabled and it's consuming far too much CPU given that it's showing as auto checks disabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1860985 Title: packagekitd using 100% CPU Status in packagekit package in Ubuntu: New Bug description: That's all I can report at this stage. Any attempt to kill it or disable the service fails and up goes its CPU usage, fans blowing the works! packagekit status give Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority after 2137ms Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh I am uid: 1000. It would be helpful if it gave some indication as to "the application". I can't find anywhere to admin this. It looks like my trust level is too low "only_trusted:0" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 Uname: Linux 5.5.0-050500rc7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 27 13:54:13 2020 InstallationDate: Installed on 2017-12-06 (782 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: packagekit UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1860985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860985] [NEW] packagekitd using 100% CPU
Public bug reported: That's all I can report at this stage. Any attempt to kill it or disable the service fails and up goes its CPU usage, fans blowing the works! packagekit status give Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority after 2137ms Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh I am uid: 1000. It would be helpful if it gave some indication as to "the application". I can't find anywhere to admin this. It looks like my trust level is too low "only_trusted:0" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 Uname: Linux 5.5.0-050500rc7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 27 13:54:13 2020 InstallationDate: Installed on 2017-12-06 (782 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: packagekit UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago) ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1860985 Title: packagekitd using 100% CPU Status in packagekit package in Ubuntu: New Bug description: That's all I can report at this stage. Any attempt to kill it or disable the service fails and up goes its CPU usage, fans blowing the works! packagekit status give Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority after 2137ms Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh I am uid: 1000. It would be helpful if it gave some indication as to "the application". I can't find anywhere to admin this. It looks like my trust level is too low "only_trusted:0" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 Uname: Linux 5.5.0-050500rc7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 27 13:54:13 2020 InstallationDate: Installed on 2017-12-06 (782 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: packagekit UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+
[Touch-packages] [Bug 1855297] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1855297/+attachment/5311418/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug 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 --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855297] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1855297/+attachment/5311417/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug 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 --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855297] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1855297/+attachment/5311416/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug 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 --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855297] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1855297/+attachment/5311415/+files/ProcEnviron.txt ** Description changed: 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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug 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
[Touch-packages] [Bug 1855297] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1855297/+attachment/5311414/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug 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 --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855297] Re: NetworkManager service fails to secure Ethernet connection when using kernel 5.4
apport information ** Tags added: apport-collected ** Description changed: 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 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1855297/+attachment/5311413/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug 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 CONNECTI
[Touch-packages] [Bug 1855297] [NEW] NetworkManager service fails to secure Ethernet connection when using kernel 5.4
Public bug reported: 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 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in network-manager package in Ubuntu: New Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
