To see the error, run: LANG=C flatpak remote-info --log flathub org.kde.Sdk//5.15 Latest commit is broken, registered as null, and presents the following output: (flatpak remote-info:44935): GLib-CRITICAL **: 17:45:31.891: g_utf8_strlen: assertion 'p != NULL || max == 0' failed Commit: (null) Parent: d14d90b6199657420def9926183e441201b48c9bbd67cb5aafc7ae5af770607c Subject: build of org.kde.Sdk, Fri 06 Nov 2020 10:10:44 PM UTC (2271c6b0e6539334dfeccd7e1ca3f358eba44be4) Date: 2020-11-07 04:26:34 +0000 History: Flatpak allows to go back one commit, but only after the package/runtime is installed. Packagers attempting to use the 5.15 Sdk and who don't already have it installed cannot install it. The error message provided when attempting to build with --install-deps-from=flathub renders: Error: Failed to install org.kde.Sdk: While trying to checkout 2a0051353a074e659ef081e7a7929553ab74569f2358ae061c1514e07d523e1d into /home/blumen/.local/share/flatpak/runtime/org.kde.Sdk/x86_64/5.15/.2a0051353a074e659ef081e7a7929553ab74569f2358ae061c1514e07d523e1d-S5FMT0: Opening content object aa3afdd282058a212b140369a8c2dc498660d95966c32ff69bdf8f2509e3eeef: Couldn't find file object 'aa3afdd282058a212b140369a8c2dc498660d95966c32ff69bdf8f2509e3eeef' Error installing deps: running `flatpak --user install flathub -y --noninteractive org.kde.Sdk/x86_64/5.15`: Child process exited with code 1
Sounds to me like an issue in flatpak. There's nothing we can change in our code to address this. And it is odd because I just upgraded and I didn't have any problems with it...
(In reply to Aleix Pol from comment #1) > Sounds to me like an issue in flatpak. There's nothing we can change in our > code to address this. Thanks for the feedback, it helped me figure out the issue. I tested this on another machine: it works there. Searching for a potential solution for a local issue, I found flatpak-repair, and their documentation explicitly mentions flatpak-repair is used to fix the flatpak installation whenever there are missing objects (in my case the commit information). A simple "flatpak repair --user" fixed things for me. If I manage to reproduce this issue again, I'll change this to resolved upstream and provide a link to the upstream (flatpak) bug report.