Bug 288380 - digikam crashes, when removing and adding tags
Summary: digikam crashes, when removing and adding tags
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Engine (show other bugs)
Version: 2.1.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-07 05:51 UTC by Axel Krebs
Modified: 2021-05-04 05:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.3.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Krebs 2011-12-07 05:51:05 UTC
Application: digikam (2.1.1)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-13-generic-pae i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

I removed and added tags with about 120 pics. 

Half of the pics ar jpg, halpf of the pics are NIKON NEF.

It looks like writing tags (metadata) into pics is very time consuming

The crash can be reproduced some of the time.

-- Backtrace:
Application: digiKam (digikam), signal: Bus error
[Current thread is 1 (Thread 0xae9468c0 (LWP 17566))]

Thread 16 (Thread 0xad6aab70 (LWP 17568)):
#0  0xb7806424 in __kernel_vsyscall ()
#1  0xb3709a5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0xb49e0cfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb4c96cc0 in wait (time=4294967295, this=0x91dc058) at thread/qwaitcondition_unix.cpp:88
#4  QWaitCondition::wait (this=0x92b6d1c, mutex=0x92b6d18, time=4294967295) at thread/qwaitcondition_unix.cpp:160
#5  0x081faf45 in Digikam::ScanController::run (this=0x923f580) at /build/buildd/digikam-2.1.1/core/digikam/database/scancontroller.cpp:647
#6  0xb4c967b3 in QThreadPrivate::start (arg=0x923f580) at thread/qthread_unix.cpp:331
#7  0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 15 (Thread 0xacea9b70 (LWP 17569)):
#0  0xb7806424 in __kernel_vsyscall ()
#1  0xb49c440e in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0xb33f234b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb33e3896 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb33e3c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb4dbfb37 in QEventDispatcherGlib::processEvents (this=0x922ba90, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0xb4d901dd in QEventLoop::processEvents (this=0xacea9100, flags=...) at kernel/qeventloop.cpp:149
#7  0xb4d90421 in QEventLoop::exec (this=0xacea9100, flags=...) at kernel/qeventloop.cpp:201
#8  0xb4c9390b in QThread::exec (this=0x927e4e0) at thread/qthread.cpp:498
#9  0xb4d70e2d in QInotifyFileSystemWatcherEngine::run (this=0x927e4e0) at io/qfilesystemwatcher_inotify.cpp:248
#10 0xb4c967b3 in QThreadPrivate::start (arg=0x927e4e0) at thread/qthread_unix.cpp:331
#11 0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 14 (Thread 0xac4ffb70 (LWP 18753)):
#0  0xb7806424 in __kernel_vsyscall ()
#1  0xb3709a5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0xb49e0cfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb4c96cc0 in wait (time=4294967295, this=0x98a6bc0) at thread/qwaitcondition_unix.cpp:88
#4  QWaitCondition::wait (this=0x98a6890, mutex=0x98a688c, time=4294967295) at thread/qwaitcondition_unix.cpp:160
#5  0xb6b5af54 in Digikam::ParkingThread::run (this=0x98a6880) at /build/buildd/digikam-2.1.1/core/libs/threads/threadmanager.cpp:119
#6  0xb4c967b3 in QThreadPrivate::start (arg=0x98a6880) at thread/qthread_unix.cpp:331
#7  0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 13 (Thread 0x9f321b70 (LWP 21403)):
#0  0xb3707dbd in pthread_mutex_lock () from /lib/i386-linux-gnu/libpthread.so.0
#1  0xb49e0f14 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6
#2  0xb33e30c3 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb33e3990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb33e3c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb4dbfb37 in QEventDispatcherGlib::processEvents (this=0xe6eb908, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0xb4d901dd in QEventLoop::processEvents (this=0x9f3210f8, flags=...) at kernel/qeventloop.cpp:149
#7  0xb4d90421 in QEventLoop::exec (this=0x9f3210f8, flags=...) at kernel/qeventloop.cpp:201
#8  0xb6b5a59e in Digikam::WorkerObjectRunnable::run (this=0xa0b811f8) at /build/buildd/digikam-2.1.1/core/libs/threads/threadmanager.cpp:196
#9  0xb4c8a651 in QThreadPoolThread::run (this=0xf353390) at concurrent/qthreadpool.cpp:106
#10 0xb4c967b3 in QThreadPrivate::start (arg=0xf353390) at thread/qthread_unix.cpp:331
#11 0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 12 (Thread 0x98a1ab70 (LWP 22160)):
#0  0xb324cd10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1
#1  0xb4ced7d5 in do_gettime (frac=0x98a19e50, sec=0x98a19e48) at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0xb4dc04b6 in QTimerInfoList::updateCurrentTime (this=0xdb3b7fc) at kernel/qeventdispatcher_unix.cpp:339
#4  0xb4dc080a in QTimerInfoList::timerWait (this=0xdb3b7fc, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0xb4dbf053 in timerSourcePrepareHelper (src=<optimized out>, timeout=0x98a19f5c) at kernel/qeventdispatcher_glib.cpp:136
#6  0xb4dbf0ed in timerSourcePrepare (source=0xdb3b7c8, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0xb33e288c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb33e3637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb33e3c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb4dbfb37 in QEventDispatcherGlib::processEvents (this=0xdef5b90, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#11 0xb4d901dd in QEventLoop::processEvents (this=0x98a1a0f8, flags=...) at kernel/qeventloop.cpp:149
#12 0xb4d90421 in QEventLoop::exec (this=0x98a1a0f8, flags=...) at kernel/qeventloop.cpp:201
#13 0xb6b5a59e in Digikam::WorkerObjectRunnable::run (this=0xe006960) at /build/buildd/digikam-2.1.1/core/libs/threads/threadmanager.cpp:196
#14 0xb4c8a651 in QThreadPoolThread::run (this=0xdf2ccd8) at concurrent/qthreadpool.cpp:106
#15 0xb4c967b3 in QThreadPrivate::start (arg=0xdf2ccd8) at thread/qthread_unix.cpp:331
#16 0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#17 0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 11 (Thread 0x96a16b70 (LWP 22464)):
[KCrash Handler]
#7  0xb39a2ddd in ?? () from /usr/lib/libexiv2.so.10
#8  0xb39a4a85 in ?? () from /usr/lib/libexiv2.so.10
#9  0xb39a4c5a in ?? () from /usr/lib/libexiv2.so.10
#10 0xb39a4dc3 in Exiv2::TiffParser::decode(Exiv2::ExifData&, Exiv2::IptcData&, Exiv2::XmpData&, unsigned char const*, unsigned int) () from /usr/lib/libexiv2.so.10
#11 0xb39a574b in Exiv2::TiffImage::readMetadata() () from /usr/lib/libexiv2.so.10
#12 0xb6e66d86 in KExiv2Iface::KExiv2::load (this=0x96a15cf0, filePath=...) at ../../libkexiv2/kexiv2.cpp:343
#13 0xb6aca53e in Digikam::DMetadata::load (this=0x96a15cf0, filePath=...) at /build/buildd/digikam-2.1.1/core/libs/dmetadata/dmetadata.cpp:106
#14 0xb6aca5b5 in Digikam::DMetadata::DMetadata (this=0x96a15cf0, filePath=...) at /build/buildd/digikam-2.1.1/core/libs/dmetadata/dmetadata.cpp:70
#15 0xb6b3361d in Digikam::ThumbnailCreator::createThumbnail (this=0x98cffc0, info=..., detailRect=..., isFace=false) at /build/buildd/digikam-2.1.1/core/libs/threadimageio/thumbnailcreator.cpp:438
#16 0xb6b34713 in Digikam::ThumbnailCreator::load (this=0x98cffc0, path=..., rect=..., pregenerate=true) at /build/buildd/digikam-2.1.1/core/libs/threadimageio/thumbnailcreator.cpp:257
#17 0xb6b35cb2 in Digikam::ThumbnailCreator::pregenerate (this=0x98cffc0, path=...) at /build/buildd/digikam-2.1.1/core/libs/threadimageio/thumbnailcreator.cpp:180
#18 0xb6b45c7d in Digikam::ThumbnailLoadingTask::execute (this=0xf17e880) at /build/buildd/digikam-2.1.1/core/libs/threadimageio/thumbnailtask.cpp:79
#19 0xb6b114e8 in Digikam::LoadSaveThread::run (this=0x98d6868) at /build/buildd/digikam-2.1.1/core/libs/threadimageio/loadsavethread.cpp:118
#20 0xb6b5c8ee in Digikam::DynamicThread::DynamicThreadPriv::run (this=0x99c2180) at /build/buildd/digikam-2.1.1/core/libs/threads/dynamicthread.cpp:328
#21 0xb4c8a651 in QThreadPoolThread::run (this=0xf5552d0) at concurrent/qthreadpool.cpp:106
#22 0xb4c967b3 in QThreadPrivate::start (arg=0xf5552d0) at thread/qthread_unix.cpp:331
#23 0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#24 0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 10 (Thread 0x959d2b70 (LWP 22465)):
#0  0xb3875ba5 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0xb3875c3e in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0xb38744d8 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 9 (Thread 0x951d1b70 (LWP 22466)):
#0  0xb3875ba5 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0xb3875c3e in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0xb38744d8 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 8 (Thread 0x949d0b70 (LWP 22467)):
#0  0xb3875ba5 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0xb3875c3e in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0xb38744d8 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 7 (Thread 0x929ccb70 (LWP 22471)):
#0  0xb3875ba5 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0xb3875c3e in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0xb38744d8 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 6 (Thread 0x921cbb70 (LWP 22472)):
#0  0xb3875ba5 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0xb3875c3e in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0xb38744d8 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 5 (Thread 0x919cab70 (LWP 22473)):
#0  0xb3875ba5 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0xb3875c3e in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0xb38744d8 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 4 (Thread 0x8524db70 (LWP 22595)):
#0  0xb3875ba5 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0xb3875c3e in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0xb38744d8 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 3 (Thread 0x84a4cb70 (LWP 22596)):
#0  0xb3875ba5 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0xb3875c3e in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0xb38744d8 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 2 (Thread 0x8424bb70 (LWP 22597)):
#0  0xb3875ba5 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0xb3875c3e in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0xb38744d8 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0xb3705d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0xb49d30ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xae9468c0 (LWP 17566)):
#0  0xb7806424 in __kernel_vsyscall ()
#1  0xb49c440e in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0xb2fac000 in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
#3  0xb2fac60c in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
#4  0xb2fac6c1 in xcb_writev () from /usr/lib/i386-linux-gnu/libxcb.so.1
#5  0xb45430d0 in _XSend () from /usr/lib/i386-linux-gnu/libX11.so.6
#6  0xb45434b8 in _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6
#7  0xb4533c88 in XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6
#8  0xb53a5c83 in x11EventSourcePrepare (s=0x9107d48, timeout=0xbf9b9b8c) at kernel/qguieventdispatcher_glib.cpp:77
#9  0xb33e288c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb33e3637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#11 0xb33e3c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#12 0xb4dbfada in QEventDispatcherGlib::processEvents (this=0x90c4038, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#13 0xb53a5e3a in QGuiEventDispatcherGlib::processEvents (this=0x90c4038, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#14 0xb4d901dd in QEventLoop::processEvents (this=0xbf9b9d64, flags=...) at kernel/qeventloop.cpp:149
#15 0xb4d90421 in QEventLoop::exec (this=0xbf9b9d64, flags=...) at kernel/qeventloop.cpp:201
#16 0xb4d9519d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#17 0xb52eb8f4 in QApplication::exec () at kernel/qapplication.cpp:3760
#18 0x080b4b64 in main (argc=) at /build/buildd/digikam-2.1.1/core/digikam/main/main.cpp:232

Possible duplicates by query: bug 263954.

Reported using DrKonqi
Comment 1 caulier.gilles 2011-12-07 06:42:08 UTC
It crash in LibExiv2. Which version you use ? Look into Help/Components Info for details...

Gilles Caulier
Comment 2 Axel Krebs 2011-12-07 15:07:00 UTC
Hi Gilles,

My components are as follows:

digiKam version 2.1.1
Exiv2 kann in JP2 speichern: Ja
Exiv2 kann in JPEG speichern: Ja
Exiv2 kann in PGF speichern: Ja
Exiv2 kann in PNG speichern: Ja
Exiv2 kann in TIFF speichern: Ja
Exiv2 unterstützt XMP-Metadaten: Ja
LibCImg: 130
LibClapack: Interne Bibliothek
LibExiv2: 0.21.1
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.7.2 (4.7.2)
LibKExiv2: 2.0.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.0.0
LibLCMS: 119
LibPGF: 6.11.24 - Interne Bibliothek
LibPNG: 1.2.46
LibQt: 4.7.4
LibRaw: 0.13.5
LibTIFF: LIBTIFF, Version 3.9.5 Copyright (c) 1988-1996 Sam Leffler
Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble-Funktion: 0.12.0 (stable release)
Parallelisiertes Entfernen von Mosaikmustern: Ja
Datenbanktreiber: QSQLITE
LibKface: 2.0.0
LibKipi: 1.2.0
LibOpenCV: 2.1.0
Libface: 0.2


Axel


Am 07.12.2011 07:42, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=288380
> 
> 
> Gilles Caulier <caulier.gilles@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |caulier.gilles@gmail.com
>           Component|general                     |Metadata
> 
> 
> 
> 
> --- Comment #1 from Gilles Caulier <caulier gilles gmail com>  2011-12-07 06:42:08 ---
> It crash in LibExiv2. Which version you use ? Look into Help/Components Info
> for details...
> 
> Gilles Caulier
>
Comment 3 caulier.gilles 2011-12-07 15:22:43 UTC
ok, Now the idea is to find which image crash Exiv2 and try to reproduce the problem using Exiv2 command line tool.

Gilles Caulier
Comment 4 Axel Krebs 2011-12-07 17:06:56 UTC
thank you for your considerations; the suggestet does not work, however.

As described before, after re-importing several collections; I observed
several sever problems; please see...

<Fwd: [Bug 283681] After re-activating several collections, a huge
number of raw pics cannot be opened>

One consequence was, that I found the same tag ("Auto") at _two places;
one at "Auto" (top level), one on "Freunde/Auto" (second level).

When removing the tag "Auto" from the secondary level (Freunde/Auto),
digiKam crashed.

Therefore I feel not able to identify "the one" responsible pic that
causes the crash (if, at all) :-(

!! Months ago, I asked for/suggested pic check to protect the complete
collection from harmful samples.

What can I do?


Axel


Am 07.12.2011 16:22, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=288380
> 
> 
> Gilles Caulier <caulier.gilles@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |ahuggel@gmx.net
> 
> 
> 
> 
> --- Comment #3 from Gilles Caulier <caulier gilles gmail com>  2011-12-07 15:22:43 ---
> ok, Now the idea is to find which image crash Exiv2 and try to reproduce the
> problem using Exiv2 command line tool.
> 
> Gilles Caulier
>
Comment 5 caulier.gilles 2011-12-10 09:10:28 UTC
Run KDEbugDialog and enable digiKam, KExiv2, KDcraw, Kipi, debug space.

From a console, run digiKam through GDB, and look debug message before than  crash appear to see which image is manage by digiKam.

Report the full trace here.

Gilles Caulier
Comment 6 Axel Krebs 2011-12-11 16:46:38 UTC
#Gilles:

as you wished... Hope this is ok.

bash: "digikam" (return): >>
ak@quadro:~$ digikam
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is
still in use, all queries will cease to work.

bash: "KExiv2" (return): >>
ak@quadro:~$ KExiv2
KExiv2: Befehl nicht gefunden.				("command not found")

bash: "KDcraw" (return): >>
ak@quadro:~$ KDcraw
KDcraw: Befehl nicht gefunden.  			("command not found")

bash: "kipi" (return): >>
ak@quadro:~$ kipi
Der Befehl »kipi« wurde nicht gefunden, meinten Sie vielleicht:
 Befehl »kiki« aus dem Paket »kiki« (universe)
kipi: Befehl nicht gefunden.

ak@quadro:~$ debug space
Der Befehl »debug« wurde nicht gefunden, meinten Sie vielleicht:
 Befehl »ebug« aus dem Paket »libdevel-ebug-perl« (universe)
 Befehl »udebug« aus dem Paket »openafs-client« (universe)
debug: Befehl nicht gefunden.

Axel

Am 10.12.2011 10:10, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=288380
> 
> 
> 
> 
> 
> --- Comment #5 from Gilles Caulier <caulier gilles gmail com>  2011-12-10 09:10:28 ---
> Run KDEbugDialog and enable digiKam, KExiv2, KDcraw, Kipi, debug space.
> 
>>From a console, run digiKam through GDB, and look debug message before than 
> crash appear to see which image is manage by digiKam.
> 
> Report the full trace here.
> 
> Gilles Caulier
>
Comment 7 caulier.gilles 2011-12-11 17:49:04 UTC
All messages are in German. I don't speak this language, i'm French...

Gilles Caulier
Comment 8 caulier.gilles 2011-12-11 19:10:36 UTC
These info are a non sence...

run kdebugdialog. It's a tool to turn on/off debug space in application as digiKam. select, "digiKam", "kexiv2", "kdcraw".

http://docs.kde.org/stable/en/kdebase-runtime/kdebugdialog/index.html

Close tool, and run digiKam from a console. Reproduce the problem and report all trace from the console here.

Gilles Caulier
Comment 9 caulier.gilles 2011-12-16 15:33:13 UTC
Axel,

What's new here ?

Gilles Caulier
Comment 10 caulier.gilles 2012-06-22 08:49:23 UTC
Official digiKam 2.6.0 release is out since few days now :

http://www.digikam.org/drupal/node/656

Please, check if this entry still valid, or update report accordingly.

Thanks in advance.

Gilles Caulier
Comment 11 caulier.gilles 2013-10-30 15:51:24 UTC
digiKam 3.5.0 is out.

Can you give a fresh feedback about your report ? Crash still reproducible ?

Thanks in advance

Gilles Caulier
Comment 12 caulier.gilles 2013-11-06 17:00:53 UTC
In all case, crash is relevant of Exiv2 shared lib. Please report this crash in Exiv2 bugzilla.

Gilles Caulier
Comment 13 caulier.gilles 2021-05-04 05:50:43 UTC
Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4