Bug 431872 - Updating the system on Opensuse Tumbleweed hangs with newest Plasma version
Summary: Updating the system on Opensuse Tumbleweed hangs with newest Plasma version
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 5.20.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-21 12:56 UTC by Tobias G.
Modified: 2021-02-01 14:48 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias G. 2021-01-21 12:56:07 UTC
SUMMARY
Trying to install updates from the system repositories on OpenSUSE Tumbleweed leads to Discover hanging at about 85%, there are no issues with flatpaks.
The updates are  installed fine.

STEPS TO REPRODUCE
1. Open Discover -> Updates
2. Install updates from system repositories
3. watch Discover hang at about 85%
4. (optional) check via "zypper dup" for updates afterwards after some time -> no updates available

OBSERVED RESULT
Discover hangs at about 85%, but updates install fine

EXPECTED RESULT
Discover installs packages without hanging at 85%

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
Operating System: openSUSE Tumbleweed 20210119
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.7-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
Memory: 23.4 GiB of RAM
Graphics Processor: GeForce GTX 1080/PCIe/SSE2

ADDITIONAL INFORMATION
This issue first occurred with Plasma 5.20.5 (I think, may have been 5.20.4), updates installed just fine with the previous version.
Comment 1 Nate Graham 2021-01-22 17:23:35 UTC
No problem using Discover on my own Tumbleweed installation, FWIW.
Comment 2 Tobias G. 2021-02-01 14:28:34 UTC
OK, I just tested it again, now it seems to work. Don't know what went wrong. :D
Am I allowed to close this thread?
Comment 3 Nate Graham 2021-02-01 14:48:29 UTC
Yeah. :)