Version: 0.9.0-svn 2006-03-19 (using KDE KDE 3.5.1) OS: Linux the topic says it all! the programm wont even start (as my last selected album contains a raw file) it looks like this: digikam: ScanLib: Finding non-existing Albums: 2222 ms digikam: ScanLib: Finding items not in the database or disk: 5417 ms digikam: ScanLib: Updating items without date: 14 ms digikam: Cannot parse EXIF metadata using Exiv2 then for all my tags warnings: "digikam: WARNING: Failed to find parent for Tag Fireworks", then: digikam: /mnt/images/photos/Misc/Test-Shots/2005-11-03/DSC_9527.NEF : RAW file identified digikam: /mnt/images/photos/Misc/Test-Shots/2005-11-03/DSC_9527.NEF : RAW file identified terminate called after throwing an instance of 'Exiv2::Error' KCrash: Application 'digikam' crashing... I think it's clear that it seems a wrong implementation of exiv2 version 0.9.1 - or a bug in that exiv2 version.. but ask me for more info!
no it's an execption generated by Exiv2 wich broke digikam. I need to drive the exception to prevent crash. Please give me a backtrace under gdb to locate the source code area relevant. Thanks in advance. Gilles Caulier
Created attachment 15222 [details] kcrash gdb crash log
But this log doesn't look useful to me.. Though I compiled digikam with --enable-debug=full
no, to make a full debug backtrace, you need to start digiKam from a gdb session. After to have install digiKam ion your system, in a console use : #gdb digikam > run > .... digikam starting... > ... > .... digikam crash !!! > bt > .... the backtrace is here (:=)))... > quit Thanks in advance Gilles Caulier
Hmm.. Now digikam doesnt really crash anymore, but freezes when I click on metadata of any file, it looks like this then(still not much info): [...] terminate called after throwing an instance of 'Exiv2::Error' Program received signal SIGABRT, Aborted. [Switching to Thread -1237178704 (LWP 8435)] 0xffffe410 in __kernel_vsyscall () (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb645164f in raise () from /lib/libc.so.6 (gdb)
Before to compile digikam including all debug info, Have you clean up all preview compilations using make distclean ? Gilles Caulier
I just did "make clean" and thought that would be enough, now after a "make distclean" and svn updating, it won't compile because of superimpose.h not found..(that's digikamimageplugins) this bug doesnt belong here, or maybe it's just me being stupid. I'm sorry.. I'll look at it when I find time...
Actually the superimpose.h has been REALY missing so this is not your fault. Was just a tired developer who worked a little to hard. It is allready in SVN so update your checkout and try it once again. I wonder why I don't have any problems with exiv2-0.9.1 and .nef files in digikam SVN?
Sorry for the bug, it seemed it was a buggy libkexif (btw, why is it still used?) But there's no exif for *.nef.. it's not implemented up to now, right? (I'll ask again in irc or so..) I mark the bug as resolved now..
no, at this time, only JPEG and CRW file are supported by Exiv2. I'm in contact with Exiv2 author to improve this point and add new file format about metadata extraction (MRW, NEF, CR2, TIFF/EP, DNG, etc)... but i will contrib to Exiv2 later than digikam 0.9.0-beta1, planed during May, depending on implementation progress. But if some others contributors wants contribe to Exiv2 lib, i will very happy (:=)))... Gilles Caulier
Not reproducible with digiKam 7.0.0-beta1.