It doesn't actually stick on any given package, it will install it when pushed to. But every time a new package is due this seems to be happening again. It seems to be happening in that gap between it deciding that there is an update there, starting to download it, but then not actually installing it until the computer is idle.
I wonder if I can simply exclude that directory from scans....?
It offered to clean up 5GB of files, but given that the system disk has currently got 1.54TB free I'm guessing that won't matter much.
|
