| Summary: | digikam crashes frequently on batch rename | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Reiner Nix <reiner.nix> |
| Component: | AdvancedRename-engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | caulier.gilles, neowalla, online |
| Priority: | NOR | ||
| Version: | 4.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.9.0 | |
| Sentry Crash Report: | |||
|
Description
Reiner Nix
2014-10-09 06:23:57 UTC
If it crash, we need a GDB backtrace to hack. See this page for details : https://www.digikam.org/contrib Hello Gilles, well prepared to pass a link with the usefull debugging howto. Here is the backtrace: (...) digikam(6098)/digikam (core) Digikam::ImageInfo::ImageInfo: No itemShortInfo could be retrieved from the database for image "2014-07-20_025.JPG" digikam(6098)/digikam (core) Digikam::ImageInfo::ImageInfo: No itemShortInfo could be retrieved from the database for image "2014-07-20_025.JPG" [Switching to Thread 0xa6b0fb40 (LWP 6103)] Catchpoint 1 (exception thrown), 0xb4c2fa06 in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6 (gdb) bt #0 0xb4c2fa06 in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #1 0xb3a01417 in Exiv2::ImageFactory::open(std::auto_ptr<Exiv2::BasicIo>) () from /usr/lib/i386-linux-gnu/libexiv2.so.13 #2 0xb3a0151f in Exiv2::ImageFactory::open(std::string const&) () from /usr/lib/i386-linux-gnu/libexiv2.so.13 #3 0xb7441574 in KExiv2Iface::KExiv2::load(QString const&) const () from /usr/lib/libkexiv2.so.11 #4 0xb710ef3e in Digikam::DMetadata::load(QString const&) const () from /usr/lib/digikam/libdigikamcore.so.4.3.0 #5 0xb6d73bba in Digikam::ImageScanner::loadFromDisk() () from /usr/lib/digikam/libdigikamdatabase.so.4.3.0 #6 0xb6d73daa in Digikam::ImageScanner::fileModified() () from /usr/lib/digikam/libdigikamdatabase.so.4.3.0 #7 0xb6cfe267 in Digikam::CollectionScanner::scanModifiedFile(QFileInfo const&, Digikam::ItemScanInfo const&) () from /usr/lib/digikam/libdigikamdatabase.so.4.3.0 #8 0xb6cfe87b in Digikam::CollectionScanner::scanFileNormal(QFileInfo const&, Digikam::ItemScanInfo const&) () from /usr/lib/digikam/libdigikamdatabase.so.4.3.0 #9 0xb6d01695 in Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&, QString const&) () from /usr/lib/digikam/libdigikamdatabase.so.4.3.0 #10 0xb6d02a3b in Digikam::CollectionScanner::partialScan(QString const&, QString const&) () from /usr/lib/digikam/libdigikamdatabase.so.4.3.0 #11 0xb6d02ca5 in Digikam::CollectionScanner::partialScan(QString const&) () from /usr/lib/digikam/libdigikamdatabase.so.4.3.0 #12 0x082312a3 in ?? () #13 0xb4dc03be in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #14 0xb36a6efb in start_thread (arg=0xa6b0fb40) at pthread_create.c:309 #15 0xb4abfd4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 (gdb) I hope that this will be helpful. Many thanks, Reiner Can you reproduce the dysfunction with current 5.8.0 pre release bundle : https://files.kde.org/digikam/ Gilles Caulier No feedback, not reproducible, and probably relevant of an older Exiv2 version. Closed. |