Summary: | Digikam crashed while scrolling through images in folder | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | admin |
Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | admin, ahuggel, caulier.gilles |
Priority: | NOR | ||
Version: | 1.2.0 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.8.0 | |
Sentry Crash Report: |
Description
admin
2010-12-05 17:05:38 UTC
Crash appear in Exiv2 library. Go to Help/components Info, and copy & paste contents here... Gilles Caulier digiKam version 1.2.0 Exiv2 can write to Jp2: Yes Exiv2 can write to Jpeg: Yes Exiv2 can write to Pgf: Yes Exiv2 can write to Png: Yes Exiv2 can write to Tiff: Yes Exiv2 supports XMP metadata: Yes LibCImg: 130 LibExiv2: 0.20 LibJPEG: 62 LibJasper: 1.900.1 LibKDE: 4.4.5 (KDE 4.4.5) LibKExiv2: 1.0.0 LibKdcraw: 1.0.0 LibLCMS: 118 LibPGF: 6.09.44 LibPNG: 1.2.44 LibQt: 4.6.3 LibRaw: 0.8.5 LibTIFF: LIBTIFF, Version 3.9.4 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Marble widget: 0.9.5 Parallelized demosaicing: Yes LibGphoto2: 2.4.6 LibKipi: 1.0.0 We need to identify the image causing the crash. Please run kdebugdialog, enable 50003. Then run digikam on the console, watch the output lines before the crash, if the filename appears. Alternatively, try with exiv2 0.21. Thanks! Does KExiv2Iface::KExiv2::getImageOrientation() have any unchecked calls to Exiv2::Exifdatum::toLong() or similar? There isn't enough info here to say for sure but this could explain the issue: http://dev.exiv2.org/issues/748#note-1 Can you reproduce the problem with the sample images from there? Andreas Yes Andreas, thank you. These calls are safe now, but the change was applied on August 23rd, way after digikam 1.2.0, so I assume this is relevant for old code and close as fixed. Dear bug reporter, feel free to reopen if you can reproduce with digikam >= 1.7.0. |