Version: (using KDE 4.3.1) OS: Linux Installed from: Mandriva RPMs DigiKam crashes after I open an album in the editor and attribute stars to images in the thumbnail strip using the mouse. I can attrbute stars to many image before it crashes. It doesn't crash at the first nor after a certain number of attributing images. Here's a backtrace: Cette pile des appels apparaît être inutilisable. C'est probablement dû au fait que votre paquetage a été construit d'une manière qui empêche de créer des piles d'appels corrects, ou que le cadre de pile a été sérieusement corrompu dans l'incident. (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) (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 0xb47068e0 (LWP 14662)] [New Thread 0xae9eab90 (LWP 15314)] [New Thread 0xafb69b90 (LWP 14684)] [New Thread 0xb1df5b90 (LWP 14665)] [New Thread 0xb25f6b90 (LWP 14664)] [New Thread 0xb3172b90 (LWP 14663)] (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) (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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe430 in __kernel_vsyscall () [Current thread is 1 (Thread 0xb47068e0 (LWP 14662))] Thread 6 (Thread 0xb3172b90 (LWP 14663)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb559fc45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb56988dd in pthread_cond_wait () from /lib/i686/libc.so.6 #3 0xb58713eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0x0828ed12 in ?? () #5 0xb58702e3 in ?? () from /usr/lib/libQtCore.so.4 #6 0xb559c315 in start_thread () from /lib/i686/libpthread.so.0 #7 0xb568b25e in clone () from /lib/i686/libc.so.6 Thread 5 (Thread 0xb25f6b90 (LWP 14664)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb559fc45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb56988dd in pthread_cond_wait () from /lib/i686/libc.so.6 #3 0xb58713eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb71e42fc in Digikam::LoadSaveThread::run () from /usr/lib/libdigikamcore.so.1 #5 0xb58702e3 in ?? () from /usr/lib/libQtCore.so.4 #6 0xb559c315 in start_thread () from /lib/i686/libpthread.so.0 #7 0xb568b25e in clone () from /lib/i686/libc.so.6 Thread 4 (Thread 0xb1df5b90 (LWP 14665)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb559fc45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb56988dd in pthread_cond_wait () from /lib/i686/libc.so.6 #3 0xb58713eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb71e42fc in Digikam::LoadSaveThread::run () from /usr/lib/libdigikamcore.so.1 #5 0xb58702e3 in ?? () from /usr/lib/libQtCore.so.4 #6 0xb559c315 in start_thread () from /lib/i686/libpthread.so.0 #7 0xb568b25e in clone () from /lib/i686/libc.so.6 Thread 3 (Thread 0xafb69b90 (LWP 14684)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb559fc45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb56988dd in pthread_cond_wait () from /lib/i686/libc.so.6 #3 0xb58713eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb71e42fc in Digikam::LoadSaveThread::run () from /usr/lib/libdigikamcore.so.1 #5 0xb58702e3 in ?? () from /usr/lib/libQtCore.so.4 #6 0xb559c315 in start_thread () from /lib/i686/libpthread.so.0 #7 0xb568b25e in clone () from /lib/i686/libc.so.6 Thread 2 (Thread 0xae9eab90 (LWP 15314)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb559fc45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb56988dd in pthread_cond_wait () from /lib/i686/libc.so.6 #3 0xb58713eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb71e42fc in Digikam::LoadSaveThread::run () from /usr/lib/libdigikamcore.so.1 #5 0xb58702e3 in ?? () from /usr/lib/libQtCore.so.4 #6 0xb559c315 in start_thread () from /lib/i686/libpthread.so.0 #7 0xb568b25e in clone () from /lib/i686/libc.so.6 Thread 1 (Thread 0xb47068e0 (LWP 14662)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb56487d6 in nanosleep () from /lib/i686/libc.so.6 #2 0xb56485be in sleep () from /lib/i686/libc.so.6 #3 0xb69758e4 in ?? () from /usr/lib/libkdeui.so.5 #4 0xb6976304 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5 #5 <signal handler called> #6 0xb72531d7 in Digikam::ThumbBarItem::repaint () from /usr/lib/libdigikamcore.so.1 #7 0x08279435 in ?? () #8 0xb72530c5 in Digikam::ThumbBarView::slotUpdate () from /usr/lib/libdigikamcore.so.1 #9 0xb7254144 in Digikam::ThumbBarView::qt_metacall () from /usr/lib/libdigikamcore.so.1 #10 0x0827c777 in ?? () #11 0xb59827d5 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb59834d5 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #13 0xb59c01b5 in QTimer::timeout () from /usr/lib/libQtCore.so.4 #14 0xb5988ee6 in QTimer::timerEvent () from /usr/lib/libQtCore.so.4 #15 0xb597d52b in QObject::event () from /usr/lib/libQtCore.so.4 #16 0xb5e3f66c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #17 0xb5e47dc6 in QApplication::notify () from /usr/lib/libQtGui.so.4 #18 0xb6904d21 in KApplication::notify () from /usr/lib/libkdeui.so.5 #19 0xb596c9de in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #20 0xb599ce4d in ?? () from /usr/lib/libQtCore.so.4 #21 0xb599962e in ?? () from /usr/lib/libQtCore.so.4 #22 0xb4c61cea in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0xb4c65354 in ?? () from /usr/lib/libglib-2.0.so.0 #24 0xb4c654df in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0xb599958a in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #26 0xb5ee43fa in ?? () from /usr/lib/libQtGui.so.4 #27 0xb596afa3 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #28 0xb596b3fd in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #29 0xb596d956 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #30 0xb5e3f4d4 in QApplication::exec () from /usr/lib/libQtGui.so.4 #31 0x082b4774 in ?? () #32 0xb55c56a5 in __libc_start_main () from /lib/i686/libc.so.6 #33 0x08088a21 in _start ()
Sound like you use digiKam 0.10.0. Right ? If yes, this bug have been fixed in current implementation (already reported...) Gilles Caulier
The backtrace seems related to bug 204871 / bug 199373 / bug 199076. The three of them are marked as FIXED/WORKSFORME. - What is your Digikam version ? (you are not using KDE4.3 but 4.2(or 4.1)) Thanks
*** Bug 216160 has been marked as a duplicate of this bug. ***
New digiKam 4.11.0 is available. https://www.digikam.org/node/740 Can you reproduce the problem with this release ?
With digiKam 5.0.0, this problem is not reproducible. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier