| Summary: | Apt Updates fail to load in Discover | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | leftcrane <leftcrane> |
| Component: | Updates | Assignee: | Dan Leinir Turthra Jensen <leinir> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | aleixpol, justin.zobel, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.15.2 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
leftcrane
2019-03-12 04:30:18 UTC
How odd! What happens if you press F5 on the updates page? It's finally working with the latest update, but it just takes about 30 seconds to load all the updates. If there is no way to make this faster (apt is lighting-fast), I'd recommend having some progress animations. Right now, it doesn't provide any indication that it's actually doing something (except a mysterious grayed out update button). (In reply to leftcrane from comment #3) > It's finally working with the latest update, but it just takes about 30 > seconds to load all the updates. > > If there is no way to make this faster (apt is lighting-fast), I'd recommend > having some progress animations. Right now, it doesn't provide any > indication that it's actually doing something (except a mysterious grayed > out update button). Me too, so I did this yeaterday: Bug 402897 Thanks for the report leftcrane, it appears this is now resolved. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks. I haven't noticed this bug recently with Discover but I also haven't been using it very much since it usually halts midway when performing updates. I've switched to native packages only because all the software stores packagekit are simply unusable. all the software stores *based* on packagekit. I've changed it to resolved, given your report and my experience (although my experience alone is insufficient, since as I said I haven't used it much.) So it's "probably" resolved. |