| Summary: | crashes during scanning albums | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | razzzat |
| Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | ahuggel, caulier.gilles, paulv |
| Priority: | NOR | ||
| Version: | 1.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.1.0 | |
| Sentry Crash Report: | |||
This looks like a duplicate of bug #204042, which is fixed in the latest version of Exiv2, 0.19, released yesterday :) Please upgrade Exiv2 and report back whether the problem still exists (you'll need to at the very least also re-compile libkexiv2). Andreas Compiled Exiv2, 0.19, but application still crashes giving the same crash report. Will try to recompile everything from scratch again to check. As usual with Ubuntu, do _not_ use an old beta5 release of digiKam, but last 1.0.0 final : http://packages.ubuntu.com/lucid/digikam Gilles Caulier Please check that the libexiv2.so file you are using when crashing (you see it in the backtrace, above it is /usr/lib/libexiv2.so.5) is indeed the one you installed when compiling 0.19. Check the file date. From the debug output on the console (run kdebugdialog to enable code 50003 before) you should be able to find out the file causing the crash and provide it here. digiKam 1.1. release will be done in few days. Please check if this entry still valid. Thanks in advance Gilles Caulier digiKam and Kipi-plugins 1.2.0 are out. Please check if crash is still valid there. Thanks in advance Gilles Caulier New Digikam user here.....what I've been able to see is awesome....with that famous BUT: Scanning files crashes Digikam a LOT, often in as little as 30 seconds. Even with repeated starts I'm only to letter F in my image folder. Many more to go. Yes, thousands of images. Compared to Picasa, the scan is slow, too. Picasa's scan seems to work completely in the background except for that little activity card that shows up in the lower right when finding new photos. Digikam's scanner sucks up a lot of resources, slowing everything down to a less than a crawl. Oh, Windows XP, SP 3, KDE 4.4.0, Digikam 1.1.0 (or whatever is current.) Right now I feel like it's dating a beautiful women with mental problems. I want, I want, I want....but.... Please provide a backtrace of your crash. So Johannes promptly responds to my email and asks for a backtrace. I send the email as return - telling him I don't have a clue what a backtrace is - and this effin' moronic bugzilla doesn't like HTML mail! WTF????????????? HEY, IT'S 2010! It's no wonder people give up on linux and open source. It's like a Mensa only secret club with archaic (non-HTML) communications. I might be sub-Mensa, but I'm close. I'm well educated, I managed a computer lab, have had a computer repair side business, and am generally looked on by friends and family as someone who can help. But here it's like I'm an illiterate noob. I guess after spending almost two hours downloading Digikam - missing files, whatever - and the constant crashing, and spending all this time finding out if this is a bug and how to report it, I'll not be using Digikam. I have too many frustrations in my life w/o adding this to it. A pity. Thanks for the caring, Johannes. The original report there is about digiKam 1.0.0-beta5 ! It's pretty old. Also the crash appear in Exiv2 shared lib. Please update digiKam to last 1.4.0 and Exiv2 to 0.20, and try again. We waiting info... Gilles Caulier New digiKam 4.11.0 is available. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? This problem is not reproducible using last digiKam 5.0.0 + Exiv2 0.25. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier |
Application that crashed: digikam Version of the application: 1.0.0-beta5 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.31-ARCH x86_64 What I was doing when the application crashed: I installed 1.0 from source. I am using Arch Linux. The probel still exist. I thought it was a bug in older version, But every time it scans album it crashes. -- Backtrace: Application: digiKam (digikam), signal: Aborted [Current thread is 1 (Thread 0x7f2f2d61b760 (LWP 24627))] Thread 2 (Thread 0x7f2f1d4cf710 (LWP 24630)): [KCrash Handler] #5 0x00007f2f265ff035 in raise () from /lib/libc.so.6 #6 0x00007f2f26600460 in abort () from /lib/libc.so.6 #7 0x00007f2f26e83925 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #8 0x00007f2f26e81d56 in __cxxabiv1::__terminate(void (*)()) () from /usr/lib/libstdc++.so.6 #9 0x00007f2f26e81d83 in std::terminate() () from /usr/lib/libstdc++.so.6 #10 0x00007f2f26e81e7e in __cxa_throw () from /usr/lib/libstdc++.so.6 #11 0x00007f2f2573347b in TXMPUtils<std::string>::ConvertToDate(char const*, XMP_DateTime*) () from /usr/lib/libexiv2.so.5 #12 0x00007f2f256a600f in Exiv2::Converter::cnvXmpDate(char const*, char const*) () from /usr/lib/libexiv2.so.5 #13 0x00007f2f2569fcca in Exiv2::Converter::cnvFromXmp() () from /usr/lib/libexiv2.so.5 #14 0x00007f2f2569fd88 in Exiv2::copyXmpToExif(Exiv2::XmpData const&, Exiv2::ExifData&) () from /usr/lib/libexiv2.so.5 #15 0x00007f2f25737f9d in Exiv2::XmpSidecar::readMetadata() () from /usr/lib/libexiv2.so.5 #16 0x00007f2f2bd4a91a in KExiv2Iface::KExiv2::load(QString const&) const () from /usr/lib/libkexiv2.so.7 #17 0x00007f2f2a88b549 in Digikam::DMetadata::load (this=0x6033, filePath=...) at /home/rajat/Downloads/digikam-1.0.0-beta5/libs/dmetadata/dmetadata.cpp:91 #18 0x00007f2f2a4a9841 in Digikam::ImageScanner::loadFromDisk (this=0x7f2f1d4ce340) at /home/rajat/Downloads/digikam-1.0.0-beta5/libs/database/imagescanner.cpp:528 #19 0x00007f2f2a4af2e8 in Digikam::ImageScanner::newFile (this=0x6033, albumId=24630) at /home/rajat/Downloads/digikam-1.0.0-beta5/libs/database/imagescanner.cpp:89 #20 0x00007f2f2a460cfb in Digikam::CollectionScanner::scanNewFile (this=0x7f2f1d4cedd0, info=..., albumId=15) at /home/rajat/Downloads/digikam-1.0.0-beta5/libs/database/collectionscanner.cpp:722 #21 0x00007f2f2a4624e9 in Digikam::CollectionScanner::scanAlbum (this=<value optimized out>, location=<value optimized out>, album=<value optimized out>) at /home/rajat/Downloads/digikam-1.0.0-beta5/libs/database/collectionscanner.cpp:637 #22 0x00007f2f2a46240b in Digikam::CollectionScanner::scanAlbum (this=<value optimized out>, location=<value optimized out>, album=<value optimized out>) at /home/rajat/Downloads/digikam-1.0.0-beta5/libs/database/collectionscanner.cpp:655 #23 0x00007f2f2a46240b in Digikam::CollectionScanner::scanAlbum (this=<value optimized out>, location=<value optimized out>, album=<value optimized out>) at /home/rajat/Downloads/digikam-1.0.0-beta5/libs/database/collectionscanner.cpp:655 #24 0x00007f2f2a462be7 in Digikam::CollectionScanner::scanAlbumRoot (this=0x7f2f1d4cedd0, location=...) at /home/rajat/Downloads/digikam-1.0.0-beta5/libs/database/collectionscanner.cpp:451 #25 0x00007f2f2a462f30 in Digikam::CollectionScanner::completeScan (this=0x7f2f1d4cedd0) at /home/rajat/Downloads/digikam-1.0.0-beta5/libs/database/collectionscanner.cpp:228 #26 0x00000000006c7932 in Digikam::ScanController::run (this=0x27d4ba0) at /home/rajat/Downloads/digikam-1.0.0-beta5/digikam/scancontroller.cpp:523 #27 0x00007f2f273452e5 in ?? () from /usr/lib/libQtCore.so.4 #28 0x00007f2f270d181a in start_thread () from /lib/libpthread.so.0 #29 0x00007f2f2669bc7d in clone () from /lib/libc.so.6 #30 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f2f2d61b760 (LWP 24627)): #0 0x00007f2f26693483 in poll () from /lib/libc.so.6 #1 0x00007f2f20b1880a in _xcb_conn_wait () from /usr/lib/libxcb.so.1 #2 0x00007f2f20b1a73c in xcb_wait_for_reply () from /usr/lib/libxcb.so.1 #3 0x00007f2f25a3ef33 in _XReply () from /usr/lib/libX11.so.6 #4 0x00007f2f25a32aa3 in XSync () from /usr/lib/libX11.so.6 #5 0x00007f2f2801be82 in ?? () from /usr/lib/libQtGui.so.4 #6 0x00007f2f28028ca7 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4 #7 0x00007f2f28050efc in ?? () from /usr/lib/libQtGui.so.4 #8 0x00007f2f219d826e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #9 0x00007f2f219dbc28 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #10 0x00007f2f219dbd50 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #11 0x00007f2f27452863 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #12 0x00007f2f280506de in ?? () from /usr/lib/libQtGui.so.4 #13 0x00007f2f27428c72 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #14 0x00007f2f27429044 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #15 0x00000000006c8bf1 in Digikam::ScanController::completeCollectionScan (this=0x27d4ba0, splash=<value optimized out>) at /home/rajat/Downloads/digikam-1.0.0-beta5/digikam/scancontroller.cpp:376 #16 0x0000000000668c93 in DigikamApp (this=0x2910740, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /home/rajat/Downloads/digikam-1.0.0-beta5/digikam/digikamapp.cpp:170 #17 0x000000000075e565 in main (argc=<value optimized out>, argv=<value optimized out>) at /home/rajat/Downloads/digikam-1.0.0-beta5/digikam/main.cpp:163 Reported using DrKonqi