Matthias Klumpp

> @ximion If that's supposed to work, I need an example on how to do that. I don't understand the documentation enough to figure that out myself. Create a directory...

Yes, that's correct. Most likely in order for this to work, you would require an actual icontheme to be present and loaded, which is not supported. I'll have a look...

If flatpak-builder or whatever runs `appstreamcli compose` passes the `--no-partial-urls` flag, all URLs will be complete and the media-baseurl will not be used, for increase backwards compatibility. That could help...

> The list view depends on a 64px icon. @ximion, any idea what to do here? Do you apply any odd configuration to appstreamcli? What is its full command-line?

Okay, that command-line looks good. A 64x64px icon should *always* be generated unconditionally, if it isn't there, compose should fail. So I guess the next thing would be to examine...

> It seems to be generated but not put into `app-info/media/com/discordapp/Discord.desktop//icons/` like 128px. Is 64px supposed to be cached only? That is expected, I think - only stuff that is...

Yeah, compose will *always* use the current component-ID for the icon name, verbatim without changing it. We had some issues in the past when compose tried to be a bit...

I too would like to solve the issues within Wayland first, for example via the proposed [xdg-placement](https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/264) protocol as well as [xdg-toplevel-icon](https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/269). Those (especially the former) are real issues that...

That makes sense! - Unfortunately we're probably not done with this, I just had Stardist process my large image (instead of just a smaller chunk of it), and it crashed...

Due to #249 actually solving the linked bug, I amended this PR to include only the Qhull update and nothing else (so, no mutex patch).