| Summary: | Digikam crash at startup while scanning files | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Amicale Salmson <amicale.salmson> |
| Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 0.9.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.3.0 | |
| Sentry Crash Report: | |||
|
Description
Amicale Salmson
2006-11-21 21:07:01 UTC
Problem already reproted. This is releavant of Exiv2 library. There is an internal bug with last Exiv2 release. Please, checkout current implementation from svn : http://www.exiv2.org/download.html ...re-compile and re-install this library, and after cleanup digiKam source code and re-compile and re-install it. Normally this will fix the problem. Note : next Exiv2 release including fix will be released at soon. Gilles Caulier Amicale, This crash still reproductible using digiKam/DigikamImagePlugins 0.9.0-RC2 and Exiv2 0.12 ? Thanks in advance for your feedback. Gilles Caulier Dunar, This crash still reproductible using digiKam/DigikamImagePlugins 0.9.0-RC2 and Exiv2 0.12 ? Thanks in advance for your feedback. Gilles Caulier Yes, it reproduces on DigiKam 0.9.0 RC2 and Exiv 0.12. I just got the same crash. I launched DigiKam and it crashed out of the blue during load. Not reproducible.
My cat was doing something funny during load, so I did not see when exactly it crashed... :)
Here is my backtrace:
Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1238239568 (LWP 24589)]
[KCrash handler]
#6 0xb63915ac in malloc_set_state () from /lib/libc.so.6
#7 0xb63917a2 in free () from /lib/libc.so.6
#8 0xb651fae1 in operator delete ()
from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libstdc++.so.6
#9 0xb64fc17d in std::string::_Rep::_M_destroy ()
from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libstdc++.so.6
#10 0xb64fece5 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string ()
from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libstdc++.so.6
#11 0xb7e74ce3 in Digikam::DMetadata::convertCommentValue (
exifDatum=@0x819ecf4) at dmetadata.cpp:1146
#12 0xb7e75679 in Digikam::DMetadata::getImageComment (this=0xbf858bb8)
at dmetadata.cpp:990
#13 0xb7d1a5e2 in Digikam::ScanLib::storeItemInDatabase (this=0xbf858f1c,
albumURL=@0xbf858ccc, filename=@0xbf858cec, albumID=16) at scanlib.cpp:415
#14 0xb7d1ab4e in Digikam::ScanLib::allFiles (this=0xbf858f1c,
directory=@0xbf858da8) at scanlib.cpp:367
#15 0xb7d22b9e in Digikam::ScanLib::findMissingItems (this=0xbf858f1c)
at scanlib.cpp:207
#16 0xb7d2532e in Digikam::ScanLib::startScan (this=0xbf858f1c)
at scanlib.cpp:100
#17 0xb7d2b1f7 in Digikam::AlbumManager::setLibraryPath (this=0x80daef8,
path=@0xbf8590dc) at albummanager.cpp:289
#18 0x0804a0d8 in main (argc=1, argv=0xbf8591d4) at main.cpp:239
Dik, if you can reproduce it, please run digiKam under valgrind like it explained at end of HACKING file and report the console messages here. Thanks in advance Gilles I've same problem... I've some structure like PictureRoot |- A | \-... | |- B .. \- G |- J .... If I set the Album Library to PictureRoot... Digikam crashs on (first scanning)... But if I test all subfolders setting as Album Library Path... All seems okay :-/ That is very confusing Here terminal output: --- SNIP --- $ digikam X Error: BadDevice, invalid or uninitialized input device 169 Major opcode: 147 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 169 Major opcode: 147 Minor opcode: 3 Resource id: 0x0 Failed to open device KCrash: Application 'digikam' crashing... --- SNAP --- Here crash trace: --- SNIP --- (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1239267664 (LWP 13959)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb62cbc2b in strlen () from /lib/tls/i686/cmov/libc.so.6 #7 0xb628375c in gettext () from /lib/tls/i686/cmov/libc.so.6 #8 0xb6282b53 in dcgettext () from /lib/tls/i686/cmov/libc.so.6 #9 0xb64b1e59 in exif_entry_get_value () from /usr/lib/libexif.so.12 #10 0xb7595a7b in KExifEntry::readEntry () from /usr/lib/libkexif.so.1 #11 0xb7595b46 in KExifEntry::setEntry () from /usr/lib/libkexif.so.1 #12 0xb7595e2b in KExifEntry::KExifEntry () from /usr/lib/libkexif.so.1 #13 0xb7597f35 in KExifIfd::setContent () from /usr/lib/libkexif.so.1 #14 0xb759810f in KExifIfd::KExifIfd () from /usr/lib/libkexif.so.1 #15 0xb7596d95 in KExifData::readFromData () from /usr/lib/libkexif.so.1 #16 0xb7e530bd in Digikam::readJPEGMetaData () from /usr/lib/libdigikam.so.0 #17 0xb7db719c in ScanLib::storeItemInDatabase () from /usr/lib/libdigikam.so.0 #18 0xb7db82c8 in ScanLib::allFiles () from /usr/lib/libdigikam.so.0 #19 0xb7db8a45 in ScanLib::findMissingItems () from /usr/lib/libdigikam.so.0 #20 0xb7db92e6 in ScanLib::startScan () from /usr/lib/libdigikam.so.0 #21 0xb7d4d677 in AlbumManager::setLibraryPath () from /usr/lib/libdigikam.so.0 #22 0x0804a3f2 in main () --- SNAP --- Here some infos: --- SNIP --- $ uname -a Linux my-lovely-linux 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007 i686 GNU/Linux --- SNAP --- I've installed Kubuntu Edgy Eft KDE Version 0.8.2 (KDE 3.5.6, Kubuntu (edgy) 4:3.5.6-0ubuntu1~edgy1) Application digiKam is a digital photo management application. More informations at http://www.digikam.org Operating System Linux (i686) release 2.6.17-11-generic Compiler Target: i486-linux-gnu Gehold, digiKam 0.8.2 is too old. digiKam 0.9.1 is out. Please update Gilles Caulier Thanks a lot... Using 0.9.1 solve this problem: http://www.mpe.mpg.de/~ach/kubuntu/edgy/Pkgs.php ok. thanks for the report Gilles Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4 |