Summary: | Aborted due to failure (While pulling ... from remote flathub: opcode set-read-source: Opening content object ...: Opening content object ...: Couldn't find file object '...') | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Timothée Ravier <travier> |
Component: | Flatpak Backend | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | aleixpol, jgrulich, madLyfe, nate, putr4.s, roshisan, travier |
Priority: | VHI | ||
Version: | 5.27.4 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Timothée Ravier
2023-04-18 15:29:10 UTC
Another way to trigger this failure is to run `flatpak update` while Discover is doing an update. *** Bug 480761 has been marked as a duplicate of this bug. *** This error is all over the internet making us look bad: https://duckduckgo.com/?q=%22aborted+due+to+failure%22&t=ffab&ia=web. My wife hits is semi-regularly too. I think we need to take greater pains to protect the user from this error, either by doing what we can on our side to fix it, or else at least wrapping it in more user-friendly padding like we do for packagekit update errors. |