Version: 1.8.0 (using KDE 4.6.0) OS: Linux Digikam apparently supports only true color images, monochrome images are displayed only in the preview pane. Reproducible: Always Steps to Reproduce: 1. Tell Ark to extract cramps.tif from pics-3.8.0.tar.gz [1]. 2. Tell showfoto to display cramps.tif. Actual Results: 1. File libtiffpic/cramps.tif 2. showfoto displays the image in the preview pane. The image pane contains the message "unable to read cramps.tif". The error log says: *** could not reset stream of /home/krzysztof/Pobrane/pakiety/libtiffpic/cramps.tif from pos 65536 to 0 after reading with TiffEndAnalyzer: Digikam::TIFFLoader::load: Can not handle image without RGB color-space: 0 *** Expected Results: 2. Let Digikam display the image in the image view. OS: Linux (x86_64) release 2.6.34.7-0.7-desktop Compiler: gcc ___ [1] <URL: ftp://ftp.remotesensing.org/pub/libtiff/pics-3.8.0.tar.gz >
There's quite a few special cases for which we dont support the TIFF specification all too well. Motivation to fix each case will dramatically increase if there is a real-world image affected.
Real-world images are affected too; however, you will have to take my word for that because the images are classified (not to be shared). OTOH, the main handler for TIFF is Okular, so it is probably not that important.
Christopher, This file still valid using digiKam 2.4 ? Gilles Caulier
What's news here using digiKam 3.1.0 ? Gilles Caulier
showfoto(5767)/digikam (core) Digikam::TIFFLoader::load: Can not handle image without RGB color-space: 0 showfoto(5767)/digikam (core) Digikam::ThumbnailCreator::createThumbnail: Cannot create thumbnail for "/tmp/kde-krzysztof/arktEPvuN/libtiffpic/cramps.tif" showfoto(5767)/digikam (core) Digikam::ThumbnailCreator::load: Thumbnail is null for "/tmp/kde-krzysztof/arktEPvuN/libtiffpic/cramps.tif" showfoto(5767)/digikam (core) Digikam::TIFFLoader::load: Can not handle image without RGB color-space: 0 showfoto(5767)/digikam (core) Digikam::DImgInterface::getImg: d->image is NULL
*** This bug has been marked as a duplicate of bug 186054 ***
Fixed with #186054