Bug 455000 - Discover's update process hangs when non-native packages (Flatpaks, add-ons) are updated
Summary: Discover's update process hangs when non-native packages (Flatpaks, add-ons) ...
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: Updates (interactive) (show other bugs)
Version: 5.24.5
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-07 21:11 UTC by Riccardo Robecchi
Modified: 2022-09-13 11:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Riccardo Robecchi 2022-06-07 21:11:59 UTC
SUMMARY
On multiple computers of mine, updating packages as well as other non-package elements like Flatpaks and add-ons (themes, icons...) leads to the update process of the packages getting stuck. To be more specific, it is the UI that gets stuck, while the actual update process goes on behind the scenes and is actually completed eventually (the dpkg process, which takes care of installing the packages, is not there).


STEPS TO REPRODUCE
1. Update both packages and non-packages, like add-ons
2. Wait for the process to finish 

OBSERVED RESULT
The process never finishes according to the UI.

EXPECTED RESULT
The UI correctly informs the user that the update process has completed.

SOFTWARE/OS VERSIONS
Linux: KDE neon
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-06-08 19:19:06 UTC
Never seen this on openSUSE or Fedora to my knowledge.
Comment 2 Riccardo Robecchi 2022-06-27 17:19:01 UTC
I can narrow it down to just add-ons, as I've recently installed Flatpaks and "normal" packages without issues. The issue appears on every computer I own (one laptop, two desktops, one tablet), so I would say it's pretty consistently reproducible.
Comment 3 Nate Graham 2022-06-28 18:18:17 UTC
So it only happens when you run `discover --backends kns-backend`?

Can you paste the terminal output from when you do so and then perform an update, triggering the hang?
Comment 4 Bug Janitor Service 2022-07-13 04:37:01 UTC
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!
Comment 5 Riccardo Robecchi 2022-07-13 10:33:35 UTC
(In reply to Nate Graham from comment #3)
> So it only happens when you run `discover --backends kns-backend`?
> 
> Can you paste the terminal output from when you do so and then perform an
> update, triggering the hang?

I've done more testing and what I found out was that the issue appears to be related to when there is a problem with the update of add-ons. When I reported the bug, the KDE add-on store was facing issues and would return errors upon trying to download new items. It's this that appears to trigger the bug: Discover would freeze its UI to when the download of add-ons failed, making it seem like the whole update process was stuck (even though it wasn't).
I haven't met this bug recently as the download of add-ons works without issues. Now, by running `plasma-discover --backends kns-backend`, everything works as intended, but it also does by running it with every backend enabled. I guess we can be sure of the cause of this bug if there are new issues with downloading add-ons, which however I don't know how to reproduce "artificially" (and I hope won't be reproduced "naturally" in the future!).
Comment 6 Riccardo Robecchi 2022-09-13 11:04:52 UTC
I haven't seen this bug for a while now, so I'm marking this as solved.