https://bugs.kde.org/show_bug.cgi?id=433587
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #9 from [email protected] --- > Yeah OK, but wouldn't it be possible to refresh when the user actually tries > to install updates then? Hi Tobias, this describes the current behaviour, no? If the user wants to install updates and/or new software, they will open Discover (which refreshes the cache) and then browse the up-to-date list of applications to install and/or click 'update all'. If they don't want to install updates and/or new software, then they won't open Discover in the first place and won't encounter this issue? I understand your frustration, but the 'forced-refresh' of the cache upon opening Discover seems intentional to me and serves a valid purpose. > The same problem occurs at the moment, when you have discover open for a few > hours and press "install updates" then. I know, not very probable, but also > not completely unthinkable. There is a 'refresh' button on the 'updates' page of Discover. I'm unaware if this was present when you first reported this ticket (version 5.21.0), but it exists now. If you are opening Discover and keeping it open, you can use it to manually refresh the cache. -- You are receiving this mail because: You are watching all bug changes.
