Bug 166867 - Digikam crashes when starting
Summary: Digikam crashes when starting
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Engine (show other bugs)
Version: 0.9.4
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-17 18:43 UTC by Chipster19
Modified: 2017-08-10 19:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 0.9.5


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chipster19 2008-07-17 18:43:27 UTC
Version:           0.9.4 (using KDE 3.5.9)
Installed from:    Compiled From Sources
Compiler:          gcc 4.3 
OS:                Linux

Following the error message :

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47353108801856 (LWP 2685)]
[KCrash handler]
#5  0x00002b1100000005 in ?? ()
#6  0x00002b113a171e82 in Exiv2::ExifTags::tagList ()
   from /usr/lib/libexiv2.so.4
#7  0x00002b113a171e9a in Exiv2::ExifTags::tagInfo ()
   from /usr/lib/libexiv2.so.4
#8  0x00002b113a1760b6 in Exiv2::ExifTags::tagName ()
   from /usr/lib/libexiv2.so.4
#9  0x00002b113a17650a in Exiv2::ExifKey::makeKey ()
   from /usr/lib/libexiv2.so.4
#10 0x00002b113a179661 in Exiv2::ExifKey::ExifKey ()
   from /usr/lib/libexiv2.so.4
#11 0x00002b113a12f592 in Exiv2::Exifdatum::Exifdatum ()
   from /usr/lib/libexiv2.so.4
#12 0x00002b113a13482e in Exiv2::ExifData::add () from /usr/lib/libexiv2.so.4
#13 0x00002b113a134d51 in Exiv2::ExifData::load () from /usr/lib/libexiv2.so.4
#14 0x00002b113a14c2f9 in Exiv2::JpegBase::readMetadata ()
   from /usr/lib/libexiv2.so.4
#15 0x00002b1139f7b643 in KExiv2Iface::KExiv2::load ()
   from /usr/lib/libkexiv2.so.3
#16 0x00002b1138745bc9 in Digikam::DMetadata::load ()
   from /usr/lib/libdigikam.so.0
#17 0x00002b1138761cab in Digikam::ImagePropertiesTab::setCurrentURL ()
   from /usr/lib/libdigikam.so.0
#18 0x00002b1138750463 in Digikam::ImagePropertiesSideBarDB::slotChangedTab ()
   from /usr/lib/libdigikam.so.0
#19 0x00002b11387507ec in Digikam::ImagePropertiesSideBarDB::itemChanged ()
   from /usr/lib/libdigikam.so.0
#20 0x00002b1138750912 in Digikam::ImagePropertiesSideBarDB::itemChanged ()
   from /usr/lib/libdigikam.so.0
#21 0x00002b11385d8ea0 in Digikam::DigikamView::slotDispatchImageSelected ()
   from /usr/lib/libdigikam.so.0
#22 0x00002b11385dc5c2 in Digikam::DigikamView::qt_invoke ()
   from /usr/lib/libdigikam.so.0
#23 0x00002b113c5ac1ac in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#24 0x00002b113c5ace23 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#25 0x00002b113c5caed5 in QTimer::event () from /usr/lib/libqt-mt.so.3
#26 0x00002b113c5570a5 in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#27 0x00002b113c557c87 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0x00002b113b8eeb1e in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#29 0x00002b113c54d9a2 in QEventLoop::activateTimers ()
   from /usr/lib/libqt-mt.so.3
#30 0x00002b113c50e7e2 in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#31 0x00002b113c56b581 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#32 0x00002b113c56b452 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#33 0x00000000004034a6 in main ()
Comment 1 Andi Clemens 2008-07-17 18:50:04 UTC
What version of libkexiv2 and exiv2 do you have installed?
Make sure to comply with the requirements listed in the README file.

Andi
Comment 2 Arnd Baecker 2008-07-17 18:51:32 UTC
To me it seems that the crash is happening inside exiv2.
Which version of exiv2 are you using (See "About digikam" menu)?
If it is not 0.17.1, please try that one).

Best, Arnd
Comment 3 Chipster19 2008-07-17 19:40:59 UTC
I have re-installed kipi-plugins version 0.1.5 and now digikam works fine !!

i have the following version of :
exiv2 : 0.17.1
kexiv2 : 0.1.7


Thanks
Chipster