Summary: | Digikam crashes whilst rebuilding missing thumbnails | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | jonnobleuk |
Component: | Plugin-DImg-RAW | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, lexa |
Priority: | NOR | ||
Version: | 1.2.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.0.0 |
Description
jonnobleuk
2010-08-19 21:35:12 UTC
crash appears in libkdcraw. sound like a binary compatibility issue in your computer. update libkdcraw and digiKam 1.3.0 Gilles Caulier There is no facility to upgrade to 1.30 due to an outstanding bug in kde-4.5. I'll rebuild the 2 and see if anything changes. I think I may have found out what the trigger for the crash is. It is libkcdraw related but in how it (or digikam) handles unusual .dng files. Namely 16bit BW .dngs. I was surprised by that type of file is possible but Vuescan allows you to do that. With the offending files included the console showed this just before the crash /media/data/images/scanned/Nikon/Scan-100810-0001.dng: Cannot use camera white balance. Scaling with darkness 0, saturation 65535, and multipliers 1.000000 28226.382812 28226.382812 28226.382812 Building histograms... /media/data/images/scanned/Nikon/Scan-100810-0001.dng: Cannot use camera white balance. Scaling with darkness 0, saturation 65535, and multipliers 1.000000 1.000000 1.000000 1.000000 Building histograms... digikam: Fatal IO error: client killed KCrash: Application 'digikam' crashing... sock_file=/home/jon/.kde4/socket-funtoo-pc/kdeinit4__0 Without that file and another 2 the crash stops. I still have those files if you want them (they're bit big) for testing. yes, we are interrested by these DNG files to test in local. It can be libraw problem indeep. Please give us external links to download these files... Which libkdcraw and libraw you use exactly ? Got Help/Components Info for details. I CC Alex who maintain libraw code for info... Gilles Caulier There's no such package as libraw in Gentoo (unless you're talking about Firewire) but from within Digikam it says it's v0.8.5. libkdcraw is v4.4.5 (kdegraphics). Components info? I'm not certain by what that exactly means. Digikam is set up with lcms and colour-management enabled; raw demosaicing is 16-bit ahd. The 2 files (75MB 7-zipped) is here: http://www.easy-share.com/1911940587/images.7z Hi! Both sample files are processed without any problems by both LibRaw 0.8.5 (mentioned above) and current LibRaw 0.10 Beta3. Have played with single-threaded Win32 version. Also, both files does not contain a thumbnail image (according to LibRaw's point of view :). As I can see in backtrace, the crash occurs in Digikam::ThumbnailCreator call. May be, digiKam has problems with images without built-in tumbnails? Thanks Alex, we will take a look. To jonnobleuk : LibRaw code in include to libkdcraw. Update Libkdcraw and digiKam and try again. I recommend to use digiKam 1.3.0 Gilles Caulier jonnobleuk, Any news there ? Can you try digiKam 1.4.0 ? Gilles Caulier Gilles, I'll give it a go at some point but it's a pita to use unstable kde packages in Fun/Gentoo. Also, i've just got my system stable and i'm kind of enjoying this novelty for now. digiKam 1.6.0 is out: http://www.digikam.org/drupal/node/550 Please update and check if this entry still valid. Thanks in advance Gilles Caulier I'd like to test it but i've lost the original images that were causing the crashes. In addition,the link for the ones I submitted is now dead. I could try to recreate them with the peculiarity e.g. missing thumbnail in a dng-raw but i have no idea how that happened in the 1st place. Ok, so we'll close this for now, if you happen to get again the test images, then please try again with newer digiKam release (currently 1.6.0) and feel free to reopen this bug with new results here New digiKam 4.11.0 is available. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier With digiKam 5.0.0, this problem is not reproducible. I close this file now. Re-open it if necessary. Gilles Caulier |