Bug 197868

Summary: Digikam crashes on startup (digikam-0.10.0-2/x86_64/Archlinux)
Product: [Applications] digikam Reporter: boris64 <bugs.kde>
Component: Metadata-EngineAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: caulier.gilles, marcel.wiesweg
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In: 1.0.0
Sentry Crash Report:

Description boris64 2009-06-25 19:39:55 UTC
Version:           digikam-0.10.0-2 (using KDE 4.2.4)
OS:                Linux
Installed from:    Unspecified Linux

Well, i can't start digikam with my picture album configured.
(digikam-0.10.0-2/x86_64/Archlinux/KDE-4.2.4)


digikam --version
-------------------------
Qt: 4.5.1
KDE: 4.2.4 (KDE 4.2.4)
digiKam: 0.10.0


Output ~/.xsession-errors
-------------------------
kdeinit4: preparing to launch /usr/bin/digikam
digikam(5804)/digikam (core) main: Root Album Path:  "/home/haselan/Bilder"
digikam(5804)/digikam (core) main: Database Path:  "/home/haselan/Bilder"
digikam(5804)/digikam (core) Digikam::SchemaUpdater::update: SchemaUpdater update
digikam(5804)/digikam (core) Digikam::SchemaUpdater::startUpdates: Have a database structure version  "5"
digikam(5804)/digikam (core) Digikam::SchemaUpdater::makeUpdates: makeUpdates  5  to  5
digikam(5804)/digikam (core) Digikam::CollectionManagerPrivate::actuallyListVolumes: listFromType
digikam(5804)/digikam (core) Digikam::CollectionManagerPrivate::actuallyListVolumes: got listFromType
digikam(5804)/digikam (core) Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location  "/haselan/Bilder"  uuid  "volumeid:?uuid=94939bbf-9e7f-47eb-9c35-79633f190b7b"
digikam(5804)/digikam (core) Digikam::CollectionManager::updateLocations: location for  "/home/haselan/Bilder"  is available  true
digikam(5804)/digikam (core) Digikam::DImg::load: "/home/haselan/Bilder/Bild0170.jpg"  : JPEG file identified
digikam: tiffcomposite.cpp:697: virtual uint32_t Exiv2::Internal::TiffMnEntry::doCount() const: Zusicherung »tiffType() == ttUndefined« nicht erfüllt.
KCrash: Application 'digikam' crashing...
-------------------------


Backtrace (via drkonqi)
-------------------------
Anwendung: digiKam (digikam), Signal SIGABRT
   from /lib/libpthread.so.0
[Current thread is 0 (LWP 5726)]

Thread 2 (Thread 0x7f4c4872c910 (LWP 5727)):
[KCrash Handler]
#5  0x00007f4c549ad2d5 in raise () from /lib/libc.so.6
#6  0x00007f4c549ae73a in abort () from /lib/libc.so.6
#7  0x00007f4c549a618a in __assert_fail () from /lib/libc.so.6
#8  0x00007f4c53ad27f3 in Exiv2::Internal::TiffMnEntry::doCount () from /usr/lib/libexiv2.so.5
#9  0x00007f4c53ad2c95 in Exiv2::Internal::TiffDirectory::writeDirEntry () from /usr/lib/libexiv2.so.5
#10 0x00007f4c53ad56e3 in Exiv2::Internal::TiffDirectory::doWrite () from /usr/lib/libexiv2.so.5
#11 0x00007f4c53ad3e2d in Exiv2::Internal::TiffSubIfd::doWriteData () from /usr/lib/libexiv2.so.5
#12 0x00007f4c53ad2238 in Exiv2::Internal::TiffDirectory::doWriteData () from /usr/lib/libexiv2.so.5
#13 0x00007f4c53ad585b in Exiv2::Internal::TiffDirectory::doWrite () from /usr/lib/libexiv2.so.5
#14 0x00007f4c53ad90c8 in Exiv2::Internal::TiffParserWorker::encode () from /usr/lib/libexiv2.so.5
#15 0x00007f4c53ad93fb in Exiv2::TiffParser::encode () from /usr/lib/libexiv2.so.5
#16 0x00007f4c53a83bcb in Exiv2::ExifParser::encode () from /usr/lib/libexiv2.so.5
#17 0x00007f4c5a00d0b5 in KExiv2Iface::KExiv2::getExif () from /usr/lib/libkexiv2.so.7
#18 0x00007f4c587c1c9a in Digikam::ImageScanner::loadFromDisk () from /usr/lib/libdigikamdatabase.so.1
#19 0x00007f4c587c8928 in Digikam::ImageScanner::newFile () from /usr/lib/libdigikamdatabase.so.1
#20 0x00007f4c587bb0ff in Digikam::CollectionScanner::scanNewFile () from /usr/lib/libdigikamdatabase.so.1
#21 0x00007f4c587bc83f in Digikam::CollectionScanner::scanAlbum () from /usr/lib/libdigikamdatabase.so.1
#22 0x00007f4c587bd267 in Digikam::CollectionScanner::scanAlbumRoot () from /usr/lib/libdigikamdatabase.so.1
#23 0x00007f4c587bd52a in Digikam::CollectionScanner::completeScan () from /usr/lib/libdigikamdatabase.so.1
#24 0x0000000000659a92 in ?? ()
#25 0x00007f4c556f0651 in ?? () from /usr/lib/libQtCore.so.4
#26 0x00007f4c5547c59a in start_thread () from /lib/libpthread.so.0
#27 0x00007f4c54a47c3d in clone () from /lib/libc.so.6
#28 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f4c5b873760 (LWP 5726)):
#0  0x00007f4c55480e99 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007f4c556f16fb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#2  0x00007f4c556f06f4 in QThread::wait () from /usr/lib/libQtCore.so.4
#3  0x00000000006585ed in ?? ()
#4  0x000000000065c61b in ?? ()
#5  0x000000000065c7b7 in ?? ()
#6  0x00007f4c549afe12 in __run_exit_handlers () from /lib/libc.so.6
#7  0x00007f4c549afe75 in exit () from /lib/libc.so.6
#8  0x00007f4c5639df58 in ?? () from /usr/lib/libQtGui.so.4
#9  0x00007f4c57756c78 in KApplication::xioErrhandler () from /usr/lib/libkdeui.so.5
#10 0x00007f4c53df953e in _XIOError () from /usr/lib/libX11.so.6
#11 0x00007f4c53e0083f in process_responses () from /usr/lib/libX11.so.6
#12 0x00007f4c53e01177 in _XEventsQueued () from /usr/lib/libX11.so.6
#13 0x00007f4c53de9e83 in XEventsQueued () from /usr/lib/libX11.so.6
#14 0x00007f4c563d6587 in ?? () from /usr/lib/libQtGui.so.4
#15 0x00007f4c53167cda in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#16 0x00007f4c531680b1 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#17 0x00007f4c531685e0 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#18 0x00007f4c5580188e in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#19 0x00007f4c563d635e in ?? () from /usr/lib/libQtGui.so.4
#20 0x00007f4c557d6ea2 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#21 0x00007f4c557d7274 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#22 0x000000000065a684 in ?? ()
#23 0x000000000061b8f4 in ?? ()
#24 0x000000000067e729 in ?? ()
#25 0x00007f4c549999ed in __libc_start_main () from /lib/libc.so.6
#26 0x0000000000458019 in _start ()
-------------------------


If you need some more useful backtrace, please give me a hint
what kind of debugging package(s) i should install. Thank you.
Thank you in advance ;)
Comment 1 Marcel Wiesweg 2009-06-25 20:25:35 UTC
Latest exiv2 (0.18.1 or 0.18.2) installed? This crash comes from exiv2 choking on an image.
Comment 2 boris64 2009-06-25 21:25:03 UTC
I have exiv2 v0.18-1 here in Archlinux (i guess "-1" is only an revision number used by the arch people).
I'll try to install the newest version (afaik v0.18.2) and will report back later.
Comment 3 boris64 2009-06-26 00:40:13 UTC
The new version of exiv2 seems to have fixed it,
i can finally start digikam again!

Thank you for your time ;)