Bug 455785 - Discover locking up doing upgrades
Summary: Discover locking up doing upgrades
Status: RESOLVED DUPLICATE of bug 455540
Alias: None
Product: Discover
Classification: Applications
Component: KNewStuff Backend (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-22 12:35 UTC by Reuben
Modified: 2022-06-24 14:00 UTC (History)
2 users (show)

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

Attachments
screenshot of issue (479.38 KB, image/png)
2022-06-22 12:35 UTC, Reuben 		Details
pkmon (6.92 KB, image/png)
2022-06-23 12:32 UTC, Reuben 		Details
startup errors (230.65 KB, image/png)
2022-06-23 12:32 UTC, Reuben 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Reuben 2022-06-22 12:35:12 UTC 
Created attachment 150048 [details]
screenshot of issue

SUMMARY
This has now happened to me twice. Discover locks up during upgrades. There are no details of what it's blocked on in the UI (this would be a useful improvement.)

STEPS TO REPRODUCE
1. Unknown. See attached screenshot. I suspect the issue has to do with the packages listed in the top section.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: kubuntu 22.04
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Comment 1 Aleix Pol 2022-06-22 13:46:40 UTC 
Once it's locked, can you try to run pkmon and see if there's ongoing transactions? Please paste the output here.
Comment 2 Nate Graham 2022-06-22 16:23:49 UTC 
.
Comment 3 Reuben 2022-06-23 12:32:35 UTC 
Created attachment 150091 [details]
pkmon
Comment 4 Reuben 2022-06-23 12:32:56 UTC 
Created attachment 150092 [details]
startup errors
Comment 5 Nate Graham 2022-06-24 14:00:48 UTC 
Ah, this is Bug 455540.

Tell your distro to upgrade their Qt patch collection; it is out of date and missing the fix for this issue.

*** This bug has been marked as a duplicate of bug 455540 ***