Summary: | If the update state is dirty, clicking on the "Update All" button triggers fetching updates rather than actually performing updates | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Leon <leon> |
Component: | Updates (interactive) | Assignee: | Aleix Pol <aleixpol> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | nate |
Priority: | VHI | Keywords: | usability |
Version: | 5.12.6 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=402928 https://bugs.kde.org/show_bug.cgi?id=407471 https://bugs.kde.org/show_bug.cgi?id=407641 |
||
Latest Commit: | Version Fixed In: | 5.17 | |
Sentry Crash Report: |
Description
Leon
2018-12-13 19:12:16 UTC
I have seen this happen in 5.14.4 too from time to time. Like Leon says, it's not consistent. 40% reproducibility feels about right though. What's happening here is that the update state is dirty, so Discover checks for updates again to get a clean state. Only *then* will it allow you to actually use the button to do what it says it will do. Needless to say, this is not ideal and will be fixed. This is no longer an issue now that we gate the update page on having all updates already collected. |