Bug 166557

Summary: Crash on manual insertation of new photos
Product: [Applications] digikam Reporter: Dotan Cohen <kde-2011.08>
Component: Metadata-EngineAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: caulier.gilles
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In: 7.1.0
Sentry Crash Report:

Description Dotan Cohen 2008-07-14 19:13:16 UTC
Version:           SVN: Version 0.10.0-beta2 (rev.: 832007) (using KDE 4.0.83)

On the current Digikam SVN I added a folder with 12 subfolders and 3 GB of photos to ~/Pictures while digikam was not running. Upon opening Digikam I got the splash screen and then it crashed with this output:

Application: digiKam (digikam), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb4d91720 (LWP 26370)]
[New Thread 0xabb33b90 (LWP 26425)]
[New Thread 0xac937b90 (LWP 26416)]
[New Thread 0xad1b3b90 (LWP 26415)]
[New Thread 0xada70b90 (LWP 26412)]
[New Thread 0xae271b90 (LWP 26411)]
[New Thread 0xaee94b90 (LWP 26410)]
[New Thread 0xaf6d7b90 (LWP 26409)]
[New Thread 0xaff3ab90 (LWP 26406)]
[New Thread 0xb2d36b90 (LWP 26405)]
[New Thread 0xb2535b90 (LWP 26404)]
[New Thread 0xb3819b90 (LWP 26371)]
[KCrash handler]
#6  0xb5004c24 in std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::find
    () from /usr/lib/kde4/lib/libexiv2.so.4
#7  0xb500138c in XMPMeta::RegisterNamespace ()
   from /usr/lib/kde4/lib/libexiv2.so.4
#8  0xb5027f98 in WXMPMeta_RegisterNamespace_1 ()
   from /usr/lib/kde4/lib/libexiv2.so.4
#9  0xb4ffbbc9 in TXMPMeta<std::string>::RegisterNamespace ()
   from /usr/lib/kde4/lib/libexiv2.so.4
#10 0xb4ff1f4d in Exiv2::XmpParser::registerNs ()
   from /usr/lib/kde4/lib/libexiv2.so.4
#11 0xb4fefae1 in Exiv2::XmpProperties::registerNs ()
   from /usr/lib/kde4/lib/libexiv2.so.4
#12 0xb56cbdd0 in KExiv2Priv (this=0x98714b8)
    at /home/hardy/digikam-notes/kdegraphics/libs/libkexiv2/libkexiv2/kexiv2private.cpp:40
#13 0xb56c8d09 in KExiv2 (this=0xbfb30894, metadata=@0xbfb308ec)
    at /home/hardy/digikam-notes/kdegraphics/libs/libkexiv2/libkexiv2/kexiv2.cpp:44
#14 0xb7da3eca in DMetadata (this=0xbfb30894)
    at /home/hardy/digikam-notes/graphics/digikam/digikam/../libs/dmetadata/dmetadata.h:47
#15 0xb7da75bd in Digikam::MetadataWidget::setMetadata (this=0x90b80d8, 
    data=@0xbfb308ec)
    at /home/hardy/digikam-notes/graphics/digikam/libs/widgets/metadata/metadatawidget.cpp:222
#16 0xb7da34c0 in Digikam::IptcWidget::loadFromURL (this=0x90b80d8, 
    url=@0xbfb309c8)
    at /home/hardy/digikam-notes/graphics/digikam/libs/widgets/metadata/iptcwidget.cpp:92
#17 0xb7dd05d7 in Digikam::ImagePropertiesMetaDataTab::setCurrentURL (
    this=0x90a65f8, url=@0xbfb309c8)
    at /home/hardy/digikam-notes/graphics/digikam/libs/imageproperties/imagepropertiesmetadatatab.cpp:151
#18 0xb7dc4b54 in Digikam::ImagePropertiesSideBar::slotNoCurrentItem (
    this=0x868a928)
    at /home/hardy/digikam-notes/graphics/digikam/libs/imageproperties/imagepropertiessidebar.cpp:112
#19 0x080be5c2 in Digikam::ImagePropertiesSideBarDB::slotNoCurrentItem (
    this=0x868a928)
    at /home/hardy/digikam-notes/graphics/digikam/libs/imageproperties/imagepropertiessidebardb.cpp:180
#20 0x080bf232 in Digikam::ImagePropertiesSideBarDB::qt_metacall (
    this=0x868a928, _c=QMetaObject::InvokeMetaMethod, _id=13, _a=0xbfb30aa8)
    at /home/hardy/digikam-notes/graphics/build/digikam/digikam/imagepropertiessidebardb.moc:110
#21 0xb67784f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#22 0xb6778bc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0x0826b4e3 in Digikam::DigikamView::signalNoCurrentItem (this=0x85c1c80)
    at /home/hardy/digikam-notes/graphics/build/digikam/digikam/digikamview.moc:341
#24 0x0826b4f8 in Digikam::DigikamView::slotThumbSizeEffect (this=0x85c1c80)
    at /home/hardy/digikam-notes/graphics/digikam/digikam/digikamview.cpp:1158
#25 0x0826c987 in Digikam::DigikamView::qt_metacall (this=0x85c1c80, 
    _c=QMetaObject::InvokeMetaMethod, _id=87, _a=0xbfb30bc8)
    at /home/hardy/digikam-notes/graphics/build/digikam/digikam/digikamview.moc:309
#26 0xb67784f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#27 0xb6778bc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#28 0xb67b5e07 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#29 0xb677f67e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#30 0xb6773c9a in QObject::event () from /usr/lib/libQtCore.so.4
#31 0xb595ac0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#32 0xb595f799 in QApplication::notify () from /usr/lib/libQtGui.so.4
#33 0xb752cd93 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#34 0xb67636a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#35 0xb67911a1 in ?? () from /usr/lib/libQtCore.so.4
#36 0xb678ea40 in ?? () from /usr/lib/libQtCore.so.4
#37 0xb51b6bf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#38 0xb51b9e5e in ?? () from /usr/lib/libglib-2.0.so.0
#39 0xb51ba3ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#40 0xb678ef98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#41 0xb59ee195 in ?? () from /usr/lib/libQtGui.so.4
#42 0xb676292d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#43 0xb6762abd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#44 0xb6764d3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#45 0xb595a567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#46 0x082918af in main (argc=5, argv=0xbfb31734)
    at /home/hardy/digikam-notes/graphics/digikam/digikam/main.cpp:298
#0  0xb7fd9410 in __kernel_vsyscall ()
Comment 1 caulier.gilles 2008-07-14 20:01:21 UTC
This crash sound the same than #166424

Gilles Caulier

*** This bug has been marked as a duplicate of 166424 ***
Comment 2 Dotan Cohen 2008-07-14 21:55:44 UTC
Thanks, Gilles. This crash happens under completely different circumstances than 166424 happens. So that I can avoid filing dupes in the future, how did you come to the conclusion that they are the same issue?
Comment 3 Andreas Huggel 2008-07-15 02:45:28 UTC
Dotan,
Can you reproduce this crash?

Andreas
Comment 4 Dotan Cohen 2008-07-15 10:15:27 UTC
No, I cannot reproduce. I have tried 16 different combinations of options and configurations (different things that I know that I have changed since this happened) but I cannot reproduce.

If I succeed in reproducing I will update the bug. Thanks.
Comment 5 caulier.gilles 2020-08-30 15:36:06 UTC
Fixed with bug #166424