Created attachment 178862 [details] Endless Fetching updates... screen SUMMARY Endless "Fetching updates..." screen. How it eas before: After I open updates tab and waiting I'm getting an error that several repositories are not updated due to expired keys or 404. I close the error popup and see the available updates. How it works now: After I open updates tab and waiting I'm getting an error that several repositories are not updated due to expired keys or 404. Once the error popup is closed, the emty "Fetching updates..." screen remains permanently. STEPS TO REPRODUCE 1. Start Discover 2. go to updates tab 3. wait OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Discover 6.3.1 Operating System: KDE neon 6.3.1 (Ubuntu 24.04.2 LTS (Noble Numbat)) KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.11.0-17-generic (64-bit) Graphics Platform: Wayland Processors: 22 × Intel® Core™ Ultra 7 155H Memory: 31.0 ГиБ of RAM Graphics Processor: Mesa Intel® Arc ADDITIONAL INFORMATION stdout: https://fars.ee/t8d2 gdb: https://fars.ee/NY8y
To me it's not endless, but it's very slow! And I don't know why because nothing else than that useless progress bar is shown. I don't know if it's my network connection. I don't know if it's the server's network connection. There are no pings, no hops, no countries, no download speeds shown. Even command line Apt is much more useful and generous with information. This is as bad as Windows' updater!
> After I open updates tab and waiting I'm getting an error that several repositories are not updated due to expired keys or 404 Well that's probably the reason, at least for your case. I guess we should show a better error message here. John, if you're seeing it be slow but not infinite, then you're encountering a different issue.
> Well that's probably the reason, at least for your case. I guess we should show a better error message here. No, that's not the reason. Everything was fine before the update. Also, this is just apt warning, not a critical malfunction.
*** This bug has been marked as a duplicate of bug 500513 ***