Bug 443878 - Discover crashes when uninstalling a Flatpak application
Summary: Discover crashes when uninstalling a Flatpak application
Status: RESOLVED DUPLICATE of bug 440877
Alias: None
Product: Discover
Classification: Applications
Component: Flatpak Backend (show other bugs)
Version: 5.22.5
Platform: openSUSE Other
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-17 08:22 UTC by Tommaso Fonda
Modified: 2021-10-17 23:25 UTC (History)
3 users (show)

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

Attachments
crash stacktrace (3.15 KB, text/vnd.kde.kcrash-report)
2021-10-17 08:22 UTC, Tommaso Fonda 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tommaso Fonda 2021-10-17 08:22:52 UTC 
Created attachment 142524 [details]
crash stacktrace

SUMMARY
Using openSUSE Tumbleweed with KDE, Discover version is 5.22.5-1.2.
When uninstalling a Flatpak application, the removing process starts, then, towards the end, Discover crashes and quits, and a KDE notification comes up saying that Discover has closed unexpectedly. The Flatpak application, however, seems to have been removed correctly. Attached is the stacktrace captured with KDE's bug reporting assistant.

STEPS TO REPRODUCE
1. Open Discover
2. Access the list of installed packages
3. Click the Remove button of any Flatpak program that is displayed in the list

OBSERVED RESULT
The progress bar appears, the Flatpak program is removed, and Discover crashes, with a notification appearing that says that Discover has closed unexpectedly.

EXPECTED RESULT
The progress bar appears, the Flatpak program is removed, and Discover continues to work normally.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Stacktrace attached.
Comment 1 Nate Graham 2021-10-17 23:25:43 UTC 

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