fedora-kde / SIG

#403 Why are we changing Discover background check-for-updates timer from 24h to 12h?
Closed: Fixed by aleasto. Opened by aleasto.

Closed: Fixed
Reopen Issue

The patch discover-5.21.4-pk_refresh_force.patch includes a change seemingly unrelated to the bug #1903294 it's fixing. On top of forcing the cache refresh to fix the bug, the timer for when DiscoverNotifier checks for updates in the background is being reduced from 24h to 12h.

I've worked to upstream the fix, which ended up looking a little different and which will now allow for much faster loading times once some dependencies get updated.

Now the question is: when we switch to the upstream patch, whether that happens naturally with Plasma 6 or we'll backport it to get faster loading times in Plasma 5, should we keep a downstream patch that changes the timer from 24h to 12h?

I believe the rationale for doing so was to ensure that it would always be checked at least once during the work day. It was also double the time that Fedora repos are set to in DNF (6h).

I'm fine either way, though I lean toward making a new smaller patch that just changes it to 12 hours and documenting it accordingly in the patch.

So i split the patches in two: https://src.fedoraproject.org/rpms/plasma-discover/pull-request/19

Metadata Update from @aleasto:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.