Bug #1098
digikam suddenly stops searching for new entries
100%
Description
digikam developers asked me to report my incident here:
First opened as [Bug 350931] in bugs.kde.org
Gilles Caulier said, that the crash is in Exiv2 .
When I start digikam it starts searching for new entries. It just stops somewhere and is no longer usable. The position and/or the image where it crashes depends on the database. I checked it with different backups as well as a new one.
Some infos about the installed software:
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(2799)/digikam (core) Digikam::DImg::load: "/run/media/andy/BILDER_03/2003/2003_10_25_Australien/2003_101_2430.CRW" : RAW file identified
digikam(2799)/digikam (core) Digikam::ImageScanner::commit: Scanning took 65 ms
digikam(2799)/digikam (core) Digikam::ImageScanner::~ImageScanner: Finishing took 319 ms
digikam(2799)/digikam (core) Digikam::DImg::load: "/run/media/andy/BILDER_03/2003/2003_10_25_Australien/2003_101_2431.CRW" : RAW file identified
digikam(2799)/digikam (core) Digikam::ImageScanner::commit: Scanning took 55 ms
digikam(2799)/digikam (core) Digikam::ImageScanner::~ImageScanner: Finishing took 291 ms
digikam(2799)/digikam (core) Digikam::DImg::load: "/run/media/andy/BILDER_03/2003/2003_10_25_Australien/2003_101_2432.CRW" : RAW file identified
digikam(2799)/digikam (core) Digikam::ImageScanner::commit: Scanning took 54 ms
digikam(2799)/digikam (core) Digikam::ImageScanner::~ImageScanner: Finishing took 188 ms
[Switching to Thread 0x7fffb705e700 (LWP 2909)]
Catchpoint 1 (exception thrown), _cxxabiv1::_cxa_throw (obj=0x7fffbc059f40, tinfo=0x7ffff7230090 <typeinfo for Exiv2::BasicError<char>>, dest=
0x7fffeffe479a <Exiv2::BasicError<char>::~BasicError()>) at
/var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/libstdc++-v3/libsupc++/eh_throw.cc:62
62 /var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/libstdc++-v3/libsupc++/eh_throw.cc: Datei oder Verzeichnis nicht gefunden.
(gdb)
And the backtrace
(gdb) bt
#0 _cxxabiv1::_cxa_throw (obj=0x7fffbc059f40, tinfo=0x7ffff7230090 <typeinfo for Exiv2::BasicError<char>>,
dest=0x7fffeffe479a <Exiv2::BasicError<char>::~BasicError()>)
at /var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/libstdc++-v3/libsupc++/eh_throw.cc:62
#1 0x00007ffff0032f45 in Exiv2::JpegBase::readMetadata (this=<optimized out>) at jpgimage.cpp:389
#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 0x00007ffff60506d8 in Digikam::DMetadata::DMetadata(QString const&) () from /usr/lib64/libdigikamcore.so.4.4.0
#5 0x00007ffff60a41cf in Digikam::ThumbnailCreator::createThumbnail(Digikam::ThumbnailInfo const&, QRect const&) const ()
from /usr/lib64/libdigikamcore.so.4.4.0
#6 0x00007ffff60a72c6 in Digikam::ThumbnailCreator::load(QString const&, QRect const&, bool) const () from /usr/lib64/libdigikamcore.so.4.4.0
#7 0x00007ffff60a7bb4 in Digikam::ThumbnailCreator::pregenerate(QString const&) const () from /usr/lib64/libdigikamcore.so.4.4.0
#8 0x00007ffff60b562a in ?? () from /usr/lib64/libdigikamcore.so.4.4.0
#9 0x00007ffff608eae2 in Digikam::LoadSaveThread::run() () from /usr/lib64/libdigikamcore.so.4.4.0
#10 0x00007ffff60baeb0 in Digikam::DynamicThread::DynamicThreadPriv::run() () from /usr/lib64/libdigikamcore.so.4.4.0
#11 0x00007ffff1f3a698 in QThreadPoolThread::run (this=0x256d130)
at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/concurrent/qthreadpool.cpp:108
#12 0x00007ffff1f45acd in QThreadPrivate::start (arg=0x256d130)
at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qthread_unix.cpp:349
#13 0x00007fffef676102 in start_thread (arg=0x7fffb705e700) at pthread_create.c:310
#14 0x00007ffff11981cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
(gdb)
This backtrace might be a bit different to the one I filed in bugs.kde.org
I checked again with my original database. Digikam stops after 93% of searching.
History
Updated by Alan Pater over 6 years ago
Andy, can you update the versions of exiv2 and digikam on your system? Both have had major upgrades since the versions you are using and these issues may already be fixed.
Updated by Andy Burger over 6 years ago
Hi Alan,
thanks for your quick answer. Regarding the updates I probably can not follow your request. I updated Gentoo's Portage tree a couple of minutes ago.
For digikam, the latest stable is still 4.4.0-r1 (Update July 27). The only non stable I could choose would be 4.6.0.
For exiv2, the latest stable is 0.24-r1 (Update August 05). There is no further release to choose.
[I] media-gfx/digikam
Available versions: (4) 3.5.0^t 4.4.0-r1^t ~4.6.0^t
{addressbook aqua debug doc gphoto2 +handbook mysql nepomuk semantic-desktop themedesigner +thumbnails video
Installed versions: 4.4.0-r1(4)^t(21:37:31 27.07.2015)(debug gphoto2 mysql semantic-desktop thumbnails video -addressbook -aqua -doc -handbook -nepomuk -themedesigner LINGUAS="de")
Homepage: http://www.digikam.org/
Description: Digital photo management application for KDE
[I] media-gfx/exiv2
Available versions: 0.23-r1 ~0.23-r2(0/12) 0.24(0/13) 0.24-r1(0/13) {contrib doc examples nls static-libs xmp zlib ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32" LINGUAS="de es fi fr pl ru sk"}
Installed versions: 0.24-r1(01:47:24 05.08.2015)(nls xmp zlib -contrib -doc -examples -static-libs ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32" LINGUAS="de")
Homepage: http://www.exiv2.org/
Description: EXIF and IPTC metadata C++ library and command line utility
I checked again all installations and found something:
I am sure that my problem started after my first install of digikam 4.4.0. My last xmp entries are from Jan 24.
The exiv2 update from 0.24 to 0.24-r1 is from Feb. 03.
Mon Dec 15 15:48:26 2014 >>> media-gfx/digikam-4.4.0-r1
Mon Mar 30 23:35:37 2015 >>> media-gfx/digikam-4.4.0-r1
Sun May 3 21:45:54 2015 >>> media-gfx/digikam-4.4.0-r1
Wed Jul 8 00:28:56 2015 >>> media-gfx/digikam-4.4.0-r1
Mon Jul 27 21:38:51 2015 >>> media-gfx/digikam-4.4.0-r1
Sat Dec 13 22:26:09 2014 >>> media-gfx/exiv2-0.24
Tue Feb 3 20:49:07 2015 >>> media-gfx/exiv2-0.24-r1
Wed Apr 1 00:12:03 2015 >>> media-gfx/exiv2-0.24-r1
Wed Aug 5 01:47:47 2015 >>> media-gfx/exiv2-0.24-r1
What I will do is to downgrade exiv2 to 0.24 and let you know if it works.
Otherwise, could you give a suggestion what digikam and exiv2 release I should wait for?
andy
Updated by Alan Pater over 6 years ago
Andy, I think you should try to get exiv2 0.25 into Gentoo.
The report for that is here: https://bugs.gentoo.org/show_bug.cgi?id=552766
As for digikam, version 4.12.0 seems to be in Gentoo unstable, but without exiv2 0.25 it may not make much difference. exiv2 0.24 is quite old, 0.25 has many, many important fixes.
Updated by Andy Burger over 6 years ago
Allright. The new ebuild for exiv2-0.25 seems to be in progress. I will just sit and wait for it. :)
So Alan, Gilles, thanks a lot for your support.
Updated by Alan Pater about 6 years ago
- Status changed from New to Resolved
- Assignee changed from Gilles Caulier to Alan Pater
- % Done changed from 0 to 90
- Estimated time set to 1.00 h
Andy, Gentoo has just updated to version 0.25 of exiv2. Can you test that and check if your issue is fixed?
Updated by Andy Burger about 6 years ago
Hi Alan,
I have finally installed exiv2-0.25-r1 and checked it for a couple of days. Everything works fine as before.
Thanks for your support.
andy
Updated by Robin Mills about 6 years ago
- Status changed from Resolved to Closed
- % Done changed from 90 to 100
Ah, this is good news. Thanks Andy. And well done Alan. I'm going to set % done to 100% and close the issue.