Summary: | digikam crashes on exiv2 error | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Rob Visser <rob.visser> |
Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | ahuggel, caulier.gilles |
Priority: | NOR | ||
Version: | 0.10.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.3.0 |
Description
Rob Visser
2008-12-26 21:58:28 UTC
Rob, I CC Andreas Huggel who is Exiv2 author. I recommend you to send to him a copy of your NEF file which crash digiKam, for future investiguations. Also, can you reproduce the crash using Exiv2 command line tool when you parse NEF file ? Thanks in advance for your help. Gilles Caulier Hi Rob, Gilles, Thanks, I have received the picture, haven't looked at it yet. This doesn't look right though. Are you sure digikam also uses version 0.18 of Exiv2? And are you sure the picture which you used with the command line utility is the one that crashes digiKam? Because - digiKam crashes somewhere inside of Exiv2::TiffImage::readMetadata - The exiv2 command line utility doesn't crash - but it uses the same call to readMetadata... Try this: 1) Ignore all errors and warnings from the exiv2 command line utility which don't crash it. (They are trying to say that the structure of the image is somehow incorrect/unexpected. But Exiv2 works around these problems and for digiKam they are transparent.) 2) Run exiv2 -v * over all your files to see if any of them crashes the application 3) Gilles, can you advise how to check which version of Exiv2 digiKam is using? Andreas Thanks Andreas, Rob, about point 3, go to Help/About menu and look in dialog which Exiv2 library is used. Gilles Caulier On Sat, Dec 27, 2008 at 8:46 PM, Rob Visser wrote: > Hi Gilles, > > Is this what you want to know? I see a suspicious 0.17 at LibExiv2: > > digiKam version 0.10.0-beta7 (rev.: 893008) > Exiv2 can write to Jp2: No > Exiv2 can write to Jpeg: Yes > Exiv2 can write to Png: No > Exiv2 can write to Tiff: No > Exiv2 support XMP metadata: Yes > LibCImg: 129 > LibExiv2: 0.17 > LibJPEG: 62 > LibJasper: 1.900.1 > LibKDE: 4.1.3 (KDE 4.1.3) > LibKExiv2: 0.5.0 > LibKdcraw: 0.4.0 > LibLCMS: 116 > LibPNG: 1.2.27 > LibQt: 4.4.3 > LibRaw: 0.6.2-Release > LibTIFF: LIBTIFF, Version 3.8.2 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. > LibGphoto2: 2.4.2 > LibKipi: 0.3.0 > > The problem probably is that there are 2 versions on exiv2 in my computer: > find . -name exiv2 > > ./usr/bin/exiv2 -> 0.17 > ./usr/local/bin/exiv2 -> 0.18 > > The latter is in my $PATH > I removed the first and made a symlink : > root@visser:/usr/bin# ls -l exiv2 > lrwxrwxrwx 1 root root 20 2008-12-27 13:39 exiv2 -> /usr/local/bin/exiv2 > > digikam still crashes on the presence of this single NEF file. Also the reported version of LibExiv2: 0.17 remains the same ?????? > Hi Rob, Yes that version 0.17 looks suspicious. Since it is in the /usr directory, it may be from your distribution. If that's the case, then the proper way to remove it is through the package management tool of your distribution. Either way, you need to remove the library, not only the command line tool: make sure there are no more files libexiv2.* in the /usr/lib directory. Then try digiKam again. I'd be surprised if it still crashes. Regards, Andreas Hello, I removed the 0.17 shared libraries, Re-compiled digikam and it works now ok. Thanks for the help Rob Visser Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4 |