Created attachment 40082 [details]
related gconf and packagekitd outputs
I'm giving a try to packagekit on my systems, but in one of them I have a problem:
$ pkcon get-time refresh-cache outputs more than 144000 seconds and augmenting, while from gconf I see that the frequency for refreshing cache is 86400 seconds as default and I've not changed it.
something that might be a key: in other system with exactly the same configuration, the refresh was performed as expected as soon as the counter reached the 86400 seconds, but in the "anomalous" system, the counter was exceeded because the computer was not running, and when was started, the timer was already higher than the limit for a cache refresh.
The expected behaviour shouldn't be that as soon as packagekit notices that he exceeded the time for a cache refresh, perform a new one refresh?
What is he waiting for?
also, Packagekit has performend some get-updates, but, logically, since the cache hasn't been refreshed, nothing happens (I know I have updates to install xD)
(Also, if I force a refresh-cache manually, everything goes as expected)
as an attachments:
the output for $gconftool-2 -R /apps/gnome-packagekit and the output of packagekitd started in verbose mode
backend in use alpm
connecting to router via wifi
As a side point: I've seen in another bug report that there's a discussion about the convenience of refreshing cache each time a get-updates is performed... well, I think that this would be the expected behaviour ;)
Thank you for your work.
Correction, I suffer the same problem on all my machines, and reaching the refresh cache time while the computer is running does not make any difference, the refresh cache time is ignored , and continues growing indefinitely.
Is gpk-update-icon running in the session of the computer that doesn't refresh?
This particular bug needs additional information to fix the bug. Please test the latest version of PackageKit and see if it fixes your problem. If it does not, please provide additional information to help the developers.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct.