Platform has no libyaml: $ flatpak run --command=sh --runtime=org.kde.Platform/x86_64/5.11 org.kde.discover ~$ ls /usr/lib/libyaml* ls: cannot access '/usr/lib/libyaml*': No such file or directory Sdk has it: $ flatpak run --command=sh --runtime=org.kde.Sdk/x86_64/5.11 org.kde.discover ~$ ls /usr/lib/libyaml* /usr/lib/libyaml-0.so.2 /usr/lib/libyaml-0.so.2.0.5 /usr/lib/libyaml.so This creates confusion for debugging the apps, since it can work on debugging stage when running from build-dir directly: $ flatpak-builder --run build-dir org.kde.discover.json plasma-discover , but the same app will not work after install: $ flatpak-builder --force-clean --install build-dir org.kde.discover.json $ flatpak run org.kde.discover org.kde.plasma.libdiscover: error loading "flatpak-backend" "Cannot load library /app/lib/plugins/discover/flatpak-backend.so: (libyaml-0.so.2: cannot open shared object file: No such file or directory)" Segmentation fault So, maybe we should add libyaml to the Platform or remove it from the SDK.
There's not much we can do about it, it's coming from org.freedesktop.Platform. If you have a compelling reason to put it in the platform, feel free to suggest it there. Note we are moving to 18.08.
Git commit 6031c0a0930ac9c06fd937b706cbf8a36a9fd63b by Aleix Pol, on behalf of Andrey Butirsky. Committed on 14/01/2019 at 18:42. Pushed by apol into branch 'master'. remove extra modules Summary: - yaml already present in SDK, but absent in Platform, so keep it meanwhile. See also: - xmlto seems unneeded Reviewers: apol Reviewed By: apol Tags: #discover_software_store Differential Revision: https://phabricator.kde.org/D17670 M +0 -9 org.kde.discover.json https://commits.kde.org/flatpak-kde-applications/6031c0a0930ac9c06fd937b706cbf8a36a9fd63b
(In reply to Aleix Pol from comment #2) > Git commit 6031c0a0930ac9c06fd937b706cbf8a36a9fd63b by Aleix Pol, on behalf > of Andrey Butirsky. > Committed on 14/01/2019 at 18:42. > Pushed by apol into branch 'master'. > > remove extra modules > > Differential Revision: https://phabricator.kde.org/D17670 > Aleix, that commit has nothing in common with this issue: that's about "xmlto" but the issue is with "libyaml". So I think it's not fixed with that commit, and I don't know if it fixed upstream at all