Summary: | Please reduce need for repo refreshes / speed them up | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | David <kitt997> |
Component: | discover | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | aleixpol, nate |
Priority: | NOR | ||
Version: | 5.25.4 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
David
2022-08-29 09:24:43 UTC
In general when this happens it's a particular backend being slow. Can you find out what it is for you?
You can find out by running Discover with only one backend at a time, e.g. `plasma-discover --backends packagekit-backend` to only use the PackageKit backend. You can find a list of installed backends with `plasma-discover --listbackends`
> Also...
Please open other bug reports for other issues.
(In reply to Nate Graham from comment #1) > In general when this happens it's a particular backend being slow. Can you > find out what it is for you? > > You can find out by running Discover with only one backend at a time, e.g. > `plasma-discover --backends packagekit-backend` to only use the PackageKit > backend. You can find a list of installed backends with `plasma-discover > --listbackends` So far what I have collected seems to indicate that it's the sum of all delays from all back-ends the problem, which could also make sense, but I'm getting different results on different tries of the same back-end. I am going to make some more tests and come back once got consistent results. > > Also... > Please open other bug reports for other issues. sure I'll do Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! (In reply to Nate Graham from comment #1) > In general when this happens it's a particular backend being slow. Can you > find out what it is for you? > > You can find out by running Discover with only one backend at a time, e.g. > `plasma-discover --backends packagekit-backend` to only use the PackageKit > backend. You can find a list of installed backends with `plasma-discover > --listbackends` > > > Also... > Please open other bug reports for other issues. Ok, after a number of tests, I can conclude PackageKit is causing the issue. Other backends all perform reliably whereas packagekit often gets stuck (and even if it does not, it's often slow). I can reproduce this behavior also from command line. At this point, I'm pretty confident it's not something Discover can take care of. But still, what do you think of tuning the need for cache refreshes so that in general they don't happen so often? Yeah that's still not ideal. That issue is more or less tracked under Bug 459207, so let's continue there. Please do file a bug on PackageKit at https://github.com/PackageKit/PackageKit/issues! *** This bug has been marked as a duplicate of bug 459207 *** (In reply to Nate Graham from comment #5) > Yeah that's still not ideal. That issue is more or less tracked under Bug > 459207, so let's continue there. Fine! > Please do file a bug on PackageKit at > https://github.com/PackageKit/PackageKit/issues! Yeah, sure. Is there any issue you have already filed or should I simply go for a new one? Go for a new one |