Hi!
Am Sa., 9. März 2024 um 04:09 Uhr schrieb Joey Hess <i...@joeyh.name>:
>
> 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
Unfortunately there isn't much we can do - this is GNOME Software
polling PackageKit again and again, and other than adding more rate
limitations, we can't fix that in PK and PK is behaving correctly.
The real solution would be to make the tool that is causing this stop
its behavior and not ask PackageKit to update the cache every second.
I reassigned it to GS, which already had a bug describing this issue exactly.
Cheers,
Matthias
--
I welcome VSRE emails. See http://vsre.info/
