https://bugs.kde.org/show_bug.cgi?id=423723
--- Comment #2 from Michael <k...@callthecomputerdoctor.com> --- Okay, what do I mean by "useful"? I mean that Discover is in a waiting state when it appears, always. How long that waiting state is, is variable. I boot my laptop. 3 minutes after the update notifier appears in the system tray, I click on the update notifier icon and Discover launches. A 27 seconds wait ensues, where Discover says "Fetching updates...". Yet my computer had just finished the fetching updates process a few minutes before. Why wait in this instance? Instead of clicking the "Update All" button at the top of Discover, I close the app. I click the update notifier once again to measure the wait. Discover launches. It takes 5 seconds of looking at the "Fetching updates..." text before I can do something. Every time I launch Discover regularly from the Kickoff menu on my SSD-backed system, Discover takes 5 seconds to display "Loading" with the spinning arrow before I could do anything. On the other hand, I launch Muon and all the packages appeared instantly when the GUI showed up. My point is that the variable waiting aspect of Discover makes me not want to reach for it, even though it is an excellently engineered piece of software in every other respect. -- You are receiving this mail because: You are watching all bug changes.
