Digikam v 2.5.0-6 Output from console is: digikam QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. digikam: Fatal IO error: client killed KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/jeff/.kde4/socket-damacas/kdeinit4__0 Below is the backtrace from KDE: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xae773880 (LWP 1938))] Thread 6 (Thread 0xad85fb40 (LWP 1940)): #0 0xb77ca424 in __kernel_vsyscall () #1 0xb41da79b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb487edbc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6 #3 0xb4b41be0 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #4 0x081f90fe in ?? () #5 0xb4b41670 in ?? () from /usr/lib/libQtCore.so.4 #6 0xb41d6ce8 in start_thread () from /lib/libpthread.so.0 #7 0xb48714de in clone () from /lib/libc.so.6 Thread 5 (Thread 0xaceffb40 (LWP 1941)): #0 0xb41d9b7e in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0 #1 0xb487f014 in pthread_mutex_unlock () from /lib/libc.so.6 #2 0xb33a35d0 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #3 0xb3363a7b in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb3363bf1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb4c82d5f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #6 0xb4c4fcfc in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #7 0xb4c4fff1 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #8 0xb4b3e2cc in QThread::exec() () from /usr/lib/libQtCore.so.4 #9 0xb4c2e4fd in ?? () from /usr/lib/libQtCore.so.4 #10 0xb4b41670 in ?? () from /usr/lib/libQtCore.so.4 #11 0xb41d6ce8 in start_thread () from /lib/libpthread.so.0 #12 0xb48714de in clone () from /lib/libc.so.6 Thread 4 (Thread 0xa663eb40 (LWP 1991)): [KCrash Handler] #6 0x0838c93d in ?? () #7 0x0839487a in ?? () #8 0x083b7df9 in ?? () #9 0x083bcea3 in ?? () #10 0xb4b41670 in ?? () from /usr/lib/libQtCore.so.4 #11 0xb41d6ce8 in start_thread () from /lib/libpthread.so.0 #12 0xb48714de in clone () from /lib/libc.so.6 Thread 3 (Thread 0xa5ca0b40 (LWP 1992)): #0 0xb48ac6d3 in __x86.get_pc_thunk.bx () from /lib/libc.so.6 #1 0xb487efe8 in pthread_mutex_unlock () from /lib/libc.so.6 #2 0xb33a35d0 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #3 0xb336397f in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb3363bf1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb4c82d5f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #6 0xb4c4fcfc in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #7 0xb4c4fff1 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #8 0xb6ad26f5 in ?? () from /usr/lib/libdigikamcore.so.2 #9 0xb4b34374 in ?? () from /usr/lib/libQtCore.so.4 #10 0xb4b41670 in ?? () from /usr/lib/libQtCore.so.4 #11 0xb41d6ce8 in start_thread () from /lib/libpthread.so.0 #12 0xb48714de in clone () from /lib/libc.so.6 Thread 2 (Thread 0xa549fb40 (LWP 1993)): #0 0xb77ca424 in __kernel_vsyscall () #1 0xb48673ab in poll () from /lib/libc.so.6 #2 0xb337219b in g_poll () from /usr/lib/libglib-2.0.so.0 #3 0xb3363a90 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb3363bf1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb4c82d5f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #6 0xb4c4fcfc in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #7 0xb4c4fff1 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #8 0xb6ad26f5 in ?? () from /usr/lib/libdigikamcore.so.2 #9 0xb4b34374 in ?? () from /usr/lib/libQtCore.so.4 #10 0xb4b41670 in ?? () from /usr/lib/libQtCore.so.4 #11 0xb41d6ce8 in start_thread () from /lib/libpthread.so.0 #12 0xb48714de in clone () from /lib/libc.so.6 Thread 1 (Thread 0xae773880 (LWP 1938)): #0 0xb77ca424 in __kernel_vsyscall () #1 0xb41da79b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb487edbc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6 #3 0xb4b41be0 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #4 0xb4b33ba3 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb4b3562c in QThreadPool::~QThreadPool() () from /usr/lib/libQtCore.so.4 #6 0xb4b35692 in QThreadPool::~QThreadPool() () from /usr/lib/libQtCore.so.4 #7 0xb4c64ca9 in QObjectPrivate::deleteChildren() () from /usr/lib/libQtCore.so.4 #8 0xb4c6a1dc in QObject::~QObject() () from /usr/lib/libQtCore.so.4 #9 0xb6ad1c98 in Digikam::ThreadManager::~ThreadManager() () from /usr/lib/libdigikamcore.so.2 #10 0xb6ad1d99 in ?? () from /usr/lib/libdigikamcore.so.2 #11 0xb68c9349 in ?? () from /usr/lib/libdigikamcore.so.2 #12 0xb47ba2e1 in __run_exit_handlers () from /lib/libc.so.6 #13 0xb47ba36d in exit () from /lib/libc.so.6 #14 0xb52359f8 in ?? () from /usr/lib/libQtGui.so.4 #15 0xb5d395d9 in KApplication::xioErrhandler(_XDisplay*) () from /usr/lib/libkdeui.so.5 #16 0xb5d39614 in ?? () from /usr/lib/libkdeui.so.5 #17 0xb435f044 in _XIOError () from /usr/lib/libX11.so.6 #18 0xb435ce4c in _XReply () from /usr/lib/libX11.so.6 #19 0xb4352263 in XQueryPointer () from /usr/lib/libX11.so.6 #20 0xb5250afb in QCursor::pos() () from /usr/lib/libQtGui.so.4 #21 0x0822bd4b in ?? () #22 0xbfb82588 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) Reproducible: Always Steps to Reproduce: 1. Plugin camera to USB 2.From KDE notifier click "Download Photos with Digikam 3. Crash Actual Results: Seg Fault 11, KDE crash report Expected Results: Connect to camera and download photos Arch Linux fully updated: KDE 4.8.3 libgphoto: 2.4.14-1 qt 4.8.1-2
Removed the ~/.kde4 directory for another reason, however, that seems to have resolved this issue.