https://bugs.kde.org/show_bug.cgi?id=456882
--- Comment #6 from Paul Krause <paul_krause_1...@t-online.de> --- Dear Charles, Dear Mike, please apologize for not responding right away. First: The bug is not completely fixed at flathub. Heic (heif-container with h265 codec) files can be decoded, but avif files (heif-container with AV1 codec) still cannot be decoded. Even though libheif claims to be able, to decode avif images, at compile time (through libaom / dav1d). I thus suspect the problem to be at digikam, QT_LOGGING states 'digikam.dimg: "example.avif" Unknown image format !!!' and like to ask: A) Should this be handled at digikam, possibly in a new issue? B) If you have any idea, or help, how to investigate this, I would appreciate it. Second: Regarding comment #5, the flatpak manifest inside the digikam repository (project/bundles/flatpak/org.kde.digikam.json, the one linked) is the reason I reported here. I do not know if this manifest is important, but if: It has two problems. If the KDE binary factory builds originate from this manifest, then I can confirm both by testing with the latest build. A) It lacks libde265 and thus heic images are not decoded. Please see this commit for a fix: https://github.com/flathub/org.kde.digikam/pull/41/commits/fe223732b7f0157a980e663e9df9bc2698246b60 I do not think, that the commit in comment #4 should fix this. I think both flathub and this fix use the same libheif. B) It cannot decode avif images. As stated before, this is still not fixed at flathub. Thanks! & Best Paul Kruse -- You are receiving this mail because: You are watching all bug changes.
