https://bugs.kde.org/show_bug.cgi?id=433587
--- Comment #6 from Tobias G. <tobi.goerg...@gmail.com> --- (In reply to Aleix Pol from comment #5) > It's not only that it's hard to fix. We used to refresh less often but then > sometimes people would get errors that their update wasn't fresh and we'd > have to tell them to F5 and try again, which is very confusing. > > In the end, even if we know that 1h ago the cache was refreshed, we can't > tell for sure that all the packages are still current. Yeah OK, but wouldn't it be possible to refresh when the user actually tries to install updates then? 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. So, instead of checking for updates when the user opens discover because he may update his system, wouldn't it be more useful to check when the user actually tries to update? And to know that updates are available, it should be checked at system boot and after a given time. And to make it less confusing for the user that when he hits "install updates" but it's checked for updates first, the text of the button could be changed to "search for updates & install", which would be better than the second solution I describe below I think. This solution here would also have nearly the same behavior as it has now, but just checks for updates when it's *really* necessary. A second usable solution would also be to check how old the cache is (like when it's 10 seconds old, it's not very probable that there're new updates), but when it's 5 or 10 minutes old, it might be necessary, so discover shows a dialog, saying that the last check for updates is XX minutes ago and new updates might be available and whether it should check for updates again or not. But that might also be confusing and just unsettle the user (and users who understand the message would probably just hit "yes" anyway all the time and then we have the same behavior as described above, just with extra steps, users who don't understand it would probably hit "no" all the time and then there might be errors with invalid updates, which confuses the user even more, so the solution described above is really better). -- You are receiving this mail because: You are watching all bug changes.
