I'm confident I saw this same problem today, with packagekit repeatedly updating and spinning a CPU for 10 minutes. It only stopped at that
point because I stopped and masked it. (Stopping it was not enough,
something was restarting the service every time I stopped it.) See
attached log.
I did not capture the trigger for that pkmon, but just before it started I had used window+s in gnome and typed in "paperwm", before remembering that doesn't find anything and pressing escape.
When I repeat that with pkmon open, I see it does trigger packagekit:
root@darkstar:/home/joey>pkmon
Transactions:
[none]
daemon connected=1
network status=online
Transactions:
1 /14317_cdeeebeb
/14317_cdeeebeb allow_cancel 1
/14317_cdeeebeb percentage -1
/14317_cdeeebeb role resolve
/14317_cdeeebeb sender /usr/bin/gnome-software
/14317_cdeeebeb status setup
It may also be relevant somehow that the topmost update was a thinkpad
AMD firmware update which "requires restart".
Joey Hess wrote:
It may also be relevant somehow that the topmost update was a thinkpad
AMD firmware update which "requires restart".
I masked and stopped packagekit again and now in gnome-software, it
displays only the thinkpad amd firmware update, and it's no longer alternating with the loading updates screen.
This makes me think that firmware update is not related to the problem.
The other updates gnome-software displays when packagekit is running are debian package updates. My last upgrade was an apt-get safe-upgrade,
because dist-upgrade wants to remove several packages, including gnome.
(I'm tracking unstable, this is typical transient dependency issues I suppose. Also I have bluez on hold at an older version due to #1060224)
So maybe gnome-software gets confused in this kind of situation and keeps retrying?
either GNOME Software is wrong (I think it unconditionally has a
problem, it should never retry a cache refresh at that insane
frequency), or the APT backend in PackageKit does something wrong and
emits package changes for blocked packages when it shouldn't do so.
I guess as soon as your system is up-to-date (with no blocked
packages), this issue will go away temporarily.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 03:19:02 |
Calls: | 6,706 |
Calls today: | 6 |
Files: | 12,235 |
Messages: | 5,350,196 |