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 (pkmon:3940508): GLib-GIO-CRITICAL **: 22:40:26.794: GTask 0x5621e2846510 (source object: 0x5621e2843330, source tag: 0x7fc2bdc121c0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program. Transactions: [none] I found similar bug reports filed on fedora, upstream, etc. Going back years. Also looking back through the journal, it's been doing this on my system for months, every week or two, generally with only a few minutes cpu time wasted per indicent. Also, I notice that when packagekit is masked, it makes apt-get update display a message to that effect. Since this bug makes masking packagekit very appealing, that is not very nice either. -- see shy jo
log.gz
Description: application/gzip
signature.asc
Description: PGP signature
