Bug 438807 - digiKam unable to display thumbnail/preview/metadata for new version KRA (Krita) documents
Summary: digiKam unable to display thumbnail/preview/metadata for new version KRA (Kri...
Status: RESOLVED DUPLICATE of bug 362999
Alias: None
Product: frameworks-kimageformats
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.80.0
Platform: Other All
: NOR normal
Target Milestone: ---
Assignee: Alex Merry
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-17 15:28 UTC by Tyson Tan
Modified: 2021-06-17 16:44 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
digiKam unable to display newer KRA file's thumbnail/preview/metadata (165.05 KB, image/png)
2021-06-17 15:28 UTC, Tyson Tan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tyson Tan 2021-06-17 15:28:40 UTC
Created attachment 139438 [details]
digiKam unable to display newer KRA file's thumbnail/preview/metadata

digiKam is current unable to display thumbnails or previews for the newer versions of KRA (Krita) documents. It doesn't even decode any of those KRA file's metadata. 

It can still decode my older KRA files. The last showing KRA file is Krita 4.3's splash saved at 2020-04-30. The next file was saved at 2020-09-14, and it is not decoded.

I think Krita updated its document format in a (not really that) recent version. It could be Krita 4.3.0 released in 2020-06-18, or 4.4.0 released in 2020-10-13. 

Maybe digiKam's related libraries are out of date?

Tested with appimage and Windows version of 7.2.0 and 7.3.0 nighties.
Comment 1 Maik Qualmann 2021-06-17 15:47:15 UTC
The Krita format is loaded by the KImageFormats plugins. Krita only uses a new ZIP code and now the bytes required to recognize the format are no longer found. There's a bug report on KImageFormats, I'm looking for ...

Maik
Comment 2 Maik Qualmann 2021-06-17 15:49:36 UTC

*** This bug has been marked as a duplicate of bug 435402 ***
Comment 3 Maik Qualmann 2021-06-17 15:51:37 UTC

*** This bug has been marked as a duplicate of bug 362999 ***
Comment 4 Tyson Tan 2021-06-17 16:44:39 UTC
Thank you Maik! :)