https://bugs.kde.org/show_bug.cgi?id=387946

--- Comment #3 from Jasper <jasper.macken...@gmail.com> ---
Please note the bug was persistent on a Digikam database that had been stable
for a very long time, and only had this years images added to it.

I tried moving all the directories on the NFS server side away, adding them one
at a time, starting digikam, letting it scan to completion, quitting digikam,
moving one more directory (one directory per year) etc.

In this way I found that the digikam scanning was failing on some very old
images, very large 20x30x300dpi TIFF's which would have been scanned a long
time ago. 

I have not found the exact file yet.
I am not sure whether this makes the current bug _solved_/_resolved_/whatever.
It would have been very useful to have some more verbose logging to know which
file it is failing on. 
Amazingly there is a lot of bitrot, with more corrupt images than I would
expect, yet digikam handled these fine.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to