I'd like to be able to use digiKam to catalog, tag, and browse Krita .kra files.

I'm running Gentoo with a previously very minimal KDE install. And previously I had installed Krita from 2.9 git in a prefix and didn't have Gwenview installed at all. At that point digiKam would find .kra files, but not show any thumbnails.

I've since installed much more of KDE, updated digiKam, and also installed Calligra/Krita 2.9.10 from Gentoo portage, along with Gwenview. And now one (1) .kra file shows a thumbnail in digiKam. But none of the other .kra files show thumbnails in digiKam.

That same .kra file shows a thumbnail in Gwenview (and that's the only .kra file that shows a thumbnail in Gwenview). That one file was created using Krita 2.9 from git and it sits next to a bunch of other .kra files saved at approximately the same time.

Anyone have any suggestions as to how to persuade digiKam to show thumbnails for .kra files? Is there a setting in Krita that creates a thumbnail?

Elle

If you open a *.kra file with an unzipper, you can see there's a 'preview.png' inside, that's what is being used for the thumbnail.

If it's missing is either a) due to autosave(We don't generate a preview during autosave because it slows down the save and causes a freeze), or b) a bug.

Hmm, I thought I had installed Calligra Krita 2.9.10 from portage, but it was only 2.8. And I had specified to not use the "kde" use flag.

Updating to the latest Calligra Krita 2.9.10 from Gentoo portage and adding the kde use flag did the trick. Now digiKam shows most .kra files with a thumbnail, and Gwenview at least shows a few.

About a third of the kra files still don't show with a thumbnail, but maybe some of those were auto-saved. Is there a way to tell if a file was auto-saved?

For all the .kra files that weren't showing digiKam thumbnails, opening with Krita, making a layer invisible and then visible again (to trigger an actual rewriting of the file), and then saving over the original file resulted in the files all having thumbnails in digiKam. So whatever the problem was when the files were saved, it isn't a problem any more.

Yes, they probably predated saving the merged image as a png inside the zip file.