| Summary: | The flatpak Backend is unable to communicate correctly with the UI of Discover and/or is unable to download (almost) anything | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Paul Degenhard <degenhardpaul> |
| Component: | Flatpak Backend | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | aleixpol, jgrulich, nate, travier |
| Priority: | NOR | ||
| Version First Reported In: | 6.2.2 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Paul Degenhard
2024-10-26 16:01:12 UTC
Does `flatpak install` in a terminal window for the same app work? Can you run Discover from a terminal window with `plasma-discover` and paste the text that appears when you reproduce the bug? I will do that after a clean re-install tomorrow. Currently, Flatpak installs from command line do work but are not detected as installed by discover (some exceptions exist though. Like mangohud...) Sounds a bit like something strange is going on, yeah. I'll interested to hear if it all goes away after a clean re-install. Will send pictures and video footage. I tested it with discord and steam beforehand. Both had the same behavior of hanging at 0%. I have a hunch that it might have to do with 32 bit architectures or something like that... Currently preparing fresh install (bad internet goes brrrrrr!). I did some digging and stumbled across the same bug appearing on a older development build. Maybe it is completely unrelated to my issue (different cause, same problems maybe?), but it could be possible that it is a resurfacing bug. Link to similar bug report: https://bugs.kde.org/show_bug.cgi?id=400389 As it turned out, the changelog of latest calamares release revealed that swap could not be created by calamares because of a bug that is now fixed in calamares 3.3.11 (2025-11-05) This bug also caused the flatpak issues |