SUMMARY Very slow start and impossible use when "fetching updates" with packagekit/dnf backend STEPS TO REPRODUCE 1. Simply start 2. wait to "fetching updates" 3. still wait ...inactive "Install buttons" 4. After 3-4 minute with hdd (and ~1min wiht SSD) finish fetching process Suggestion Do not start "Fetching updates" every time when start Discover OR Add a option for "Prevenet auto fetching updates" for discover start Regards OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.19.4/5.72.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION This problem still exists in all previous version as well
What distro are you using? We made significant improvements here in Plasma 5.20 for all distros.
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!
Sorry if I'm too late, we are very busy now. So the problem: too much transaction started by Discover in same time, please watch this videorecord. The distro is blackPanther OS. affected versions: 16-18-20devel I tried present all issue in this video: https://youtu.be/_p-NvozDMMc if you have any other information you need, please detail me what should i send for you can fix this problem.
Your video appears to show pkcon operations taking ages and ages and ages. Since pkcon is a simple CLI frontend to packagekit, and Discover is a GUI frontend to packagekit, then it would make sense that Discover's operations would similarly take forever and ever; Discover can't be faster than PackageKit itself is! :) So in both cases the solution is the same: fix the performance of the PackageKit plugin for the distro itself. It's also possible that there's some kind of packaging misconfiguration that's causing it to be slow. It's definitely not that slow on any distro I've ever used Discover on (Neon, Manjaro, openSUSE Tumbleweed).
Please watch previous video until the end... In first minutes I tried to show you, that PackageKit is fast and working correctly, but Discover via PackageKit plugin is not fast, very slow because discover start ~400 transaction in same time. "s definitely not that slow on any distro I've ever used Discover on (Neon, Manjaro, openSUSE Tumbleweed)." These distro does not use Discover->PackageKit->DNF plugins. (The URPMI plugin is worse than DNF.) So, I tried Gnome-Software, the situation is same: PackageKit->DNF pluging, and working fine and fast, it becomes immediately usable after start. Please watch this video too: https://youtu.be/92R_P70_4mw Maybe now it is clearly shown that the error is in Discover. "fix the performance of the PackageKit plugin for the distro itself" Yes, maybe, I tried looking for a solution, but something another bug always intervened to find this problem...
The bug is really resolved in 5.20.x Discover starts is very fast now, it's so really user friendly Thank You!
You're welcome!