[Touch-packages] [Bug 1860985] Re: packagekitd using 100% CPU

2020-03-31 Thread Launchpad Bug Tracker
[Expired for packagekit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: packagekit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. h

[Touch-packages] [Bug 1860985] Re: packagekitd using 100% CPU

2020-01-31 Thread Owen
It's off again, this time an opensuse repository. I would remove it about now but it seems it can't be removed without breaking other stuff. The following packages will be REMOVED apturl gnome-packagekit gnome-software gnome-software-plugin-flatpak gnome-software-plugin-snap gstreamer1.0-packag

[Touch-packages] [Bug 1860985] Re: packagekitd using 100% CPU

2020-01-27 Thread Julian Andres Klode
Well, we can't discuss two issues in one bug. The setting is completely irrelevant for PackageKit, as that controls APT's downloading of new update information. That said, I think we did override that somewhere so that PackageKit does not download it either. Please open a separate bug report for th

[Touch-packages] [Bug 1860985] Re: packagekitd using 100% CPU

2020-01-27 Thread Owen
The PPA was deb [arch=amd64] http://dl.google.com/linux/webdesigner/deb/ stable main The linked ticket does sound like the issue, but my other concern is despite setting the "Automatically check for updates" to "Never" is Software and Updates the system continues to look for update at quite a high

[Touch-packages] [Bug 1860985] Re: packagekitd using 100% CPU

2020-01-27 Thread Julian Andres Klode
Bugs happen, but w/o being able to reproduce them, there's not much we can do here. What was the PPA that caused this? It does sound like I fixed this upstream: https://github.com/hughsie/PackageKit/pull/321/commits/9a2eab81a792b6ff55950fd53ee76a481f331d9f ** Changed in: packagekit (Ubuntu)

[Touch-packages] [Bug 1860985] Re: packagekitd using 100% CPU

2020-01-27 Thread Owen Savill
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 wh