Summary: | Random crashes of digikam | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Mark van Rossum <mark.vanrossum> |
Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | ahuggel, caulier.gilles |
Priority: | NOR | ||
Version: | 1.2.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.5.0 | |
Sentry Crash Report: |
Description
Mark van Rossum
2010-05-18 15:20:51 UTC
Crash come from Exiv2 library. Which Exiv2 version you use ? Go to Help/Components Info for details Please try to identify which file is relevant of this crash. In your backtrace, i can see that a JPEG file is parsed. Try to reproduce the crash using Exiv2 command line tool. Which camera you use ? Nikon ? If yes, there is an important fix in current implementation of Exiv2 from svn trunk about Nikon. I recommend to try this code (libkexiv2 + digiKam and co need to be recompiled of course) Gilles Caulier Yes, it is a Nikon. But note that digikam crashes not always on the same picture. Flipping to the photos with great speed seems to cause it. Sorry, but won't have time to recompile everything from source. Libexiv version is 0.19. Running exivtool on all jpg's is fine exivtool -a -u -g1 ~/Pictures/x/* No. Exiv2 command line tool is... exiv2 (:=))). You have used exiftool, which is a Perl metadata management program. Exiv2 is a pure C++ libray to manage metadata. there is also a command line tool provided. Gilles Caulier Ok, I ran exiv2 * no problems were detected *** Bug 238623 has been marked as a duplicate of this bug. *** Can you try to update digiKam to 1.4.0 and libexiv2 to 0.20 ? Gilles Caulier I have 1.40 and don't have this bug anymore. I guess it can be closed. Thanks |