Created attachment 132860 [details] Discover stuck SUMMARY I use Arch distribution. Today I decided to use Discover for update of packages. BTW. Is not possible to disable it in TA permanently shows its icon in Taskbar every Plasma update, even I disable it "System Tray Settings", only needs set "Always hidden". Maybe this is defined in package present in my distribution. Unfortunately it stuck during of installing the Addons. I don't know which type, because Discover doesn't show information if this is theme, icons or cursors. Details please find in attached screenshot. Note that the window was hanging about half an hour. Showing no error, no progress, nothing. Of course internet connection was fine. Cancel button didn't work. Only closing window after using "Quit anyway" helped. In attached screen looks like because of addons would be blocked other packages, but this wasn't truth. I started different package manager application (pamac) and turned out that system is up-to-date. So seems Discover didn't refresh properly the list of packages to update. Only correctly shown information in status bar saying: "Updates (2)", which of course were these 2 addons. STEPS TO REPRODUCE Having addons not up-to-date and some packages to update 1. Start Discover (placed in taskbar) for update 2. Click "Update All" 3. Wait OBSERVED RESULT Discover stuck with update of some addons. Only closing application helps. EXPECTED RESULT Discover should not stuck with update of any addons, and show any error, message that something went wrong. SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75 Qt Version: 5.15.1 ADDITIONAL INFORMATION
I did it again. This time I noticed at bottom of window appeared some error, only it was visible through very short time (I think 2 seconds). It wasn't highlighted with red background so wasn't so much visible, but the worse is that it disappeared very quickly. I don't understand why here error is not embedded on bottom or top of main window (with "x" closing it) to user was aware that something went wrong. Of course situation repeated, again two addons blocked refreshing of list updated other (system) packages - pamac shows that nothing to update.
I can reproduce same behaviour and I think I realise what might be happening. When you install an icon theme, for instance, it can have different versions of it, a dark and a light version, or maybe different release version, so a menu asking to choose a version appears. I think discover expects the same and so it get stucks because is waiting for your choose which is not showing on screen BTW. Sorry for my english :)
(In reply to utomas from comment #2) > I can reproduce same behaviour and I think I realise what might be happening. > > When you install an icon theme, for instance, it can have different versions > of it, a dark and a light version, or maybe different release version, so a > menu asking to choose a version appears. I think discover expects the same > and so it get stucks because is waiting for your choose which is not showing > on screen BTW. > > Sorry for my english :) This is original report, but I created also duplicated one (I forgot about this one) which has been took into account by developers and I thins issue has been fixed. I didn't test it yet, because no happened update for stuff which cased the issue for me. Please check Bug 430812 for details. And back to this report. You are right. Sometimes happens that exists two or more versions of the same package (dark and light or more colours), and Discover is not (or, considering Bug 430812, wasn't) able to match proper one, so didn't update an interface, but the update was still in progress, only we didn't see it. I was wrong saying that update stuck. After enough of time when we wait, update might pass with success. After we close Discover and open again turns out that system is up to date. I discovered that to unblock such stuck progress (in the middle of update), needs to open "System Settings" go to proper configuration, check update and in"New Stuff" tool and click update there. And then after back to Discover turns out that progress is showing correctly. Shortly. The issue was that Discover wasn't able to interpret correctly the answer from external system, and just not updated progress bar, but he skipped this package and was going further. I think this was fixed already. Check my another bug report. https://bugs.kde.org/show_bug.cgi?id=430812 I change status of this one as resolved, because this report is a duplication. *** This bug has been marked as a duplicate of bug 430812 ***