https://bugs.kde.org/show_bug.cgi?id=402425
Bug ID: 402425
Summary: kde.Platform has no libyaml but kde.Sdk has it
Product: flatpak-platform-plugin
Version: unspecified
Platform: Flatpak
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jgrul...@redhat.com
Reporter: butir...@gmail.com
CC: aleix...@kde.org
Target Milestone: ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
