Version: (using KDE 4.2.4) OS: Linux Installed from: Mandriva RPMs After downloading pics from an attached camera (D90), have finished with the download and closed app via close menu entry. Application: digiKam (digikam), signal SIGABRT [Current thread is 1 (Thread 0xb47ff8e0 (LWP 8855))] Thread 1 (Thread 0xb47ff8e0 (LWP 8855)): [KCrash Handler] #6 0xffffe424 in __kernel_vsyscall () #7 0xb56d2c00 in raise () from /lib/i686/libc.so.6 #8 0xb56d4668 in abort () from /lib/i686/libc.so.6 #9 0xb5961c45 in qt_message_output () from /usr/lib/libQtCore.so.4 #10 0xb5961d3c in qFatal () from /usr/lib/libQtCore.so.4 #11 0xb6d58e5c in KIO::Scheduler::cancelJob () from /usr/lib/libkio.so.5 #12 0xb6caa729 in KIO::SimpleJob::doKill () from /usr/lib/libkio.so.5 #13 0xb5ca4832 in KJob::kill () from /usr/lib/libkdecore.so.5 #14 0x08207222 in ?? () #15 0x0820bd08 in ?? () #16 0x0820bf37 in ?? () #17 0xb56d5cd9 in exit () from /lib/i686/libc.so.6 #18 0xb56bf6ad in __libc_start_main () from /lib/i686/libc.so.6 #19 0x08088a21 in _start ()
This is likely to be bug 197622. - What is your Digikam version ? Thanks
digiKam Version 0.10.0 Using KDE 4.2.4 (KDE 4.2.4)
Unless a stack trace with debug info for digikam proves different, marking as duplicate *** This bug has been marked as a duplicate of bug 197622 ***
Since digiKam 5.0.0, we drop KIO slave in favor of a multi-threaded interface to query the database. This problem will not reproducible.