Fix for missing icons: Require Qt SVG plug-in #60
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bugzilla
https://bugzilla.suse.com/show_bug.cgi?id=1114654
Trello
https://trello.com/c/27ozQgUS/452-ostumbleweed-p1-1114654-build-20181102-patternselector-icons-missing-openqa-test-fails-in-selectpatternsandpackages
Problem
No status icons in the patterns or package selector in Qt, in the inst-sys as well as in the installed system later.
Cause
No support for SVG available. We have compiled-in fallback icons, but they are also SVG now, so they cannot be rendered or maybe even not loaded.
In previous versions, the libyui-qt-pkg plugin was linked against libqt5svg.so (it was listed in the
ldd
) output, but since this current Tumbleweed snapshot it is no longer. Why this is so is not completely clear; very likely it was an indirect dependency where some other part of Qt was using it. Even trying to force linking it to libyui-qt-pkg failed every time; we are not actively using it, only indirectly, and it is a plug-in to the Qt image loading subsystem; so the linker saw our link instruction and still decided that it is not necessary and simply did not link that lib to our binary (I tried different approaches with that).Solution
Add a plain and simple explicit
Requires
for the package (not the library) to our .spec file.In the inst-sys
@wfeldt said if we have that dependency on our package it will automatically be honored for building the inst-sys.