Bug 443175

Summary:	Discover updates get stuck with no message
Product:	[Applications] Discover	Reporter:	David <david.cortes.rivera>
Component:	discover	Assignee:	Dan Leinir Turthra Jensen <leinir>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	aleixpol, nate
Priority:	NOR
Version First Reported In:	5.21.5
Target Milestone:	---
Platform:	Debian unstable
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description David 2021-09-30 22:29:02 UTC

SUMMARY
At random times, when updating packages through discover, it will get stuck without being able to complete some step, and without showing anything about its status other than an empty bar "Installing" next to each package (typically stuck at over 90% in the progress bar at the left pane). This is after it has already downloaded all the relevant packages. The "cancel" button is not clickable when this happens, although the app is responsive and I can do other things with it. I'd have to guess it might be running some CLI app behind the scenes that requires user input to continue, but the GUI is not aware of such fact.

STEPS TO REPRODUCE
Not sure.

OBSERVED RESULT
Gets stuck during package updates.

EXPECTED RESULT
Should not get stuck during packages updates, and should always allow seeing what's going on behind the scenes, and allow cancelling (which it doesn't when it gets stuck).

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

Comment 1 Aleix Pol 2021-10-01 01:22:14 UTC

Do you know if it's a specific package that it gets stuck on?
You can try running pkmon to see what transaction packagekit is stuck on. If it's any of the other backends you should be able to easily identify it in the UI.

Comment 2 David 2021-10-01 01:24:21 UTC

(In reply to Aleix Pol from comment #1)
> Do you know if it's a specific package that it gets stuck on?
> You can try running pkmon to see what transaction packagekit is stuck on. If
> it's any of the other backends you should be able to easily identify it in
> the UI.

Last time happened with google-chrome, other times has happened with linux-image and related.

Comment 3 Nate Graham 2021-10-05 00:18:25 UTC

Yes, when this happens, can you run `pkmon` in a terminal window and report what it says? That should show the last thing it started to work on, at least.

Comment 4 Bug Janitor Service 2021-10-20 04:35:30 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 Bug Janitor Service 2021-11-04 04:35:25 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!