Bug 350931 - digiKam suddenly stops searching for new entries
Summary: digiKam suddenly stops searching for new entries
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Engine (show other bugs)
Version: 4.4.0
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-03 19:12 UTC by andy
Modified: 2021-04-25 08:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.3.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andy 2015-08-03 19:12:36 UTC
When I start digikam it usually starts searching for new entries. Some day it started but stopped after a short time of searching. It just stops after e.g. 13% of searching and crashes. Chrashes means, it is still there but no longer usable. 

What I did so far:
System update
digikam reinstall
searched the web --> nothing
used gdb (see below)


Reproducible: Always

Steps to Reproduce:
I simply reproduce ist like this:
1. I put all new pictures (CR2) in specific subdirectories on an external HDD
2. start digikam
3. digikam starts searching for new entries
4. after a while ist just stops. With existing database after 91%. With new database after 13%. So actually on different places in the db and different pictures.

Actual Results:  
digikam just stops and hangs somehow. If I stop the process i am not able to access any album and I do not see any thumbnails.

Expected Results:  
Import all pictures into the db.

Some infos about the system:
Linux biohazard 4.0.5-gentoo-mykernel-nvidia #2 SMP Fri Jul 31 23:25:53 CEST 2015 x86_64 Intel(R) Pentium(R) 4 CPU 3.20GHz GenuineIntel GNU/Linux
Digikam installed versions:  4.4.0-r1(4)^t(21:37:31 27.07.2015)(debug gphoto2 mysql semantic-desktop thumbnails video
gcc Installed versions:  4.8.4(4.8)^s(02:34:06 15.06.2015)(cxx fortran multilib nls nptl openmp sanitize

Here are the last lines of the debugger:


digikam(3010)/digikam (core) Digikam::ImageScanner::prepareAddImage: Adding new item 
"/run/media/andy/BILDER_03/2003/2003_10_25_Australien/Panorama/2003_101_1535_1539_panorama.jpg"
digikam(3010)/digikam (core) Digikam::ImageScanner::scanTags: Pick Label found :  0
digikam(3010)/digikam (core) Digikam::ImageScanner::scanTags: Assigned Pick Label Tag  :  20
digikam(3010)/digikam (core) Digikam::ImageScanner::scanTags: Color Label found :  0
digikam(3010)/digikam (core) Digikam::ImageScanner::scanTags: Assigned Color Label Tag  :  10
digikam(3010)/digikam (core) Digikam::DMetadata::getImageHistory: Loading image history  ""
digikam(3010)/digikam (core) Digikam::ImageScanner::commit: Scanning took 123 ms
digikam(3010)/digikam (core) Digikam::ImageScanner::~ImageScanner: Finishing took 1 ms
digikam(3010)/digikam (core) Digikam::DImg::load: "/run/media/andy/BILDER_03/2003/2003_10_25_Australien/Panorama/2003_101_1535_1539_panorama.tif"  : 
TIFF file identified
digikam(3010)/digikam (core) Digikam::ImageScanner::prepareAddImage: Adding new item 
"/run/media/andy/BILDER_03/2003/2003_10_25_Australien/Panorama/2003_101_1535_1539_panorama.tif"
digikam(3010)/digikam (core) Digikam::ImageScanner::scanTags: Pick Label found :  0
digikam(3010)/digikam (core) Digikam::ImageScanner::scanTags: Assigned Pick Label Tag  :  20
digikam(3010)/digikam (core) Digikam::ImageScanner::scanTags: Color Label found :  0
digikam(3010)/digikam (core) Digikam::ImageScanner::scanTags: Assigned Color Label Tag  :  10
digikam(3010)/digikam (core) Digikam::DMetadata::getImageHistory: Loading image history  ""
digikam(3010)/digikam (core) Digikam::ImageScanner::commit: Scanning took 93 ms
digikam(3010)/digikam (core) Digikam::ImageScanner::~ImageScanner: Finishing took 1 ms
[Switching to Thread 0x7fffd70b4700 (LWP 3014)]
Catchpoint 1 (exception thrown), 0x00007ffff19b719f in __cxa_throw () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/libstdc++.so.6


This is the backtrace:

(gdb) bt
#0  0x00007ffff19b719f in __cxa_throw () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/libstdc++.so.6
#1  0x00007ffff0032f45 in Exiv2::JpegBase::readMetadata() () from /usr/lib64/libexiv2.so.13
#2  0x00007ffff6fbbfaa in KExiv2Iface::KExiv2::load(QString const&) const () from /usr/lib64/libkexiv2.so.11
#3  0x00007ffff605066a in Digikam::DMetadata::load(QString const&) const () from /usr/lib64/libdigikamcore.so.4.4.0
#4  0x00007ffff65fb020 in Digikam::ImageScanner::loadFromDisk() () from /usr/lib64/libdigikamdatabase.so.4.4.0
#5  0x00007ffff65fb1d0 in Digikam::ImageScanner::newFile(int) () from /usr/lib64/libdigikamdatabase.so.4.4.0
#6  0x00007ffff6593a6e in Digikam::CollectionScanner::scanNewFile(QFileInfo const&, int) () from /usr/lib64/libdigikamdatabase.so.4.4.0
#7  0x00007ffff6596f54 in Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&, QString const&) ()
   from /usr/lib64/libdigikamdatabase.so.4.4.0
#8  0x00007ffff6596e82 in Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&, QString const&) ()
   from /usr/lib64/libdigikamdatabase.so.4.4.0
#9  0x00007ffff6596e82 in Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&, QString const&) ()
   from /usr/lib64/libdigikamdatabase.so.4.4.0
#10 0x00007ffff6596e82 in Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&, QString const&) ()
   from /usr/lib64/libdigikamdatabase.so.4.4.0
#11 0x00007ffff659762d in Digikam::CollectionScanner::scanAlbumRoot(Digikam::CollectionLocation const&) () from 
/usr/lib64/libdigikamdatabase.so.4.4.0
#12 0x00007ffff659894e in Digikam::CollectionScanner::completeScan() () from /usr/lib64/libdigikamdatabase.so.4.4.0
#13 0x00000000005f5566 in ?? ()
#14 0x00007ffff1f45acd in ?? () from /usr/lib64/qt4/libQtCore.so.4
#15 0x00007fffef676102 in start_thread () from /lib64/libpthread.so.0
#16 0x00007ffff11981cd in clone () from /lib64/libc.so.6
(gdb)
Comment 1 caulier.gilles 2015-08-06 07:52:56 UTC
Crash is in Exiv2 shared library when JPEG image is parsed. Please report this problem to Exiv2 bugzilla with full GDB backtrace and image file relevant when you read image with Exiv2 CLI tool. 

http://dev.exiv2.org/projects/exiv2/issues

Gilles Caulier
Comment 2 caulier.gilles 2021-04-25 08:26:43 UTC
Problem is no longer reproducible with digiKam 7.3.0 and Exiv2 0.27.4