Application: digikam (2.2.0) KDE Platform Version: 4.7.2 (4.7.2) "release 5" Qt Version: 4.7.4 Operating System: Linux 3.1.0-1.2-desktop x86_64 Distribution: "openSUSE 12.1 (x86_64)" -- Information about the crash: The application was importing a new library (first start of application). Since the % of scan was always at 0% I've closed Digikam and it crashed. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault [Current thread is 1 (Thread 0x7f0cac5647e0 (LWP 29803))] Thread 3 (Thread 0x7f0c8fde3700 (LWP 29805)): #0 0x00007f0ca5d21423 in poll () from /lib64/libc.so.6 #1 0x00007f0c9dfa0a98 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f0c9dfa0f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f0ca77fb576 in QEventDispatcherGlib::processEvents (this=0x7f0c800008c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424 #4 0x00007f0ca77cfa22 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f0ca77cfc1f in QEventLoop::exec (this=0x7f0c8fde2d70, flags=...) at kernel/qeventloop.cpp:201 #6 0x00007f0ca76e75df in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498 #7 0x00007f0ca77b2aef in QInotifyFileSystemWatcherEngine::run (this=0xe08a80) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x00007f0ca76ea025 in QThreadPrivate::start (arg=0xe08a80) at thread/qthread_unix.cpp:331 #9 0x00007f0ca3a99f05 in start_thread () from /lib64/libpthread.so.0 #10 0x00007f0ca5d2a53d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f0c8f5e2700 (LWP 29809)): #0 0x00007f0ca3a9de6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f0ca76ea4bb in wait (time=18446744073709551615, this=0x120f120) at thread/qwaitcondition_unix.cpp:88 #2 QWaitCondition::wait (this=<optimized out>, mutex=0x120eca8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160 #3 0x00007f0ca9e0ad67 in ?? () from /usr/lib64/libdigikamcore.so.2 #4 0x00007f0ca76ea025 in QThreadPrivate::start (arg=0x120ec90) at thread/qthread_unix.cpp:331 #5 0x00007f0ca3a99f05 in start_thread () from /lib64/libpthread.so.0 #6 0x00007f0ca5d2a53d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f0cac5647e0 (LWP 29803)): [KCrash Handler] #6 0x000000000064f454 in ?? () #7 0x00000000005786c5 in ?? () #8 0x000000000058752d in ?? () #9 0x00007f0ca77e359a in QMetaObject::activate (sender=0x1e39020, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffa7a3b5e0) at kernel/qobject.cpp:3287 #10 0x00007f0ca69215d2 in QAction::triggered (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qaction.cpp:263 #11 0x00007f0ca69217bf in QAction::activate (this=0x1e39020, event=<optimized out>) at kernel/qaction.cpp:1257 #12 0x00007f0ca6d57969 in QMenuPrivate::activateCausedStack (this=0x20ac780, causedStack=..., action=0x1e39020, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1005 #13 0x00007f0ca6d5d5a2 in QMenuPrivate::activateAction (this=0x20ac780, action=0x1e39020, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1097 #14 0x00007f0ca82e3d40 in KMenu::mouseReleaseEvent (this=0x19a4a10, e=0x7fffa7a3c1b0) at /usr/src/debug/kdelibs-4.7.2/kdeui/widgets/kmenu.cpp:464 #15 0x00007f0ca69782b6 in QWidget::event (this=0x19a4a10, event=0x7fffa7a3c1b0) at kernel/qwidget.cpp:8295 #16 0x00007f0ca6d5eb0b in QMenu::event (this=0x19a4a10, e=0x7fffa7a3c1b0) at widgets/qmenu.cpp:2405 #17 0x00007f0ca6927be4 in notify_helper (e=0x7fffa7a3c1b0, receiver=0x19a4a10, this=0xb7c910) at kernel/qapplication.cpp:4481 #18 QApplicationPrivate::notify_helper (this=0xb7c910, receiver=0x19a4a10, e=0x7fffa7a3c1b0) at kernel/qapplication.cpp:4453 #19 0x00007f0ca692d36b in QApplication::notify (this=<optimized out>, receiver=0x19a4a10, e=0x7fffa7a3c1b0) at kernel/qapplication.cpp:4042 #20 0x00007f0ca8221e36 in KApplication::notify (this=0x7fffa7a3cfc0, receiver=0x19a4a10, event=0x7fffa7a3c1b0) at /usr/src/debug/kdelibs-4.7.2/kdeui/kernel/kapplication.cpp:311 #21 0x00007f0ca77d081c in QCoreApplication::notifyInternal (this=0x7fffa7a3cfc0, receiver=0x19a4a10, event=0x7fffa7a3c1b0) at kernel/qcoreapplication.cpp:787 #22 0x00007f0ca6928bb2 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:215 #23 QApplicationPrivate::sendMouseEvent (receiver=0x19a4a10, event=0x7fffa7a3c1b0, alienWidget=0x0, nativeWidget=0x19a4a10, buttonDown=0x0, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3141 #24 0x00007f0ca69a5201 in QETWidget::translateMouseEvent (this=0x19a4a10, event=<optimized out>) at kernel/qapplication_x11.cpp:4406 #25 0x00007f0ca69a3a2a in QApplication::x11ProcessEvent (this=0x7fffa7a3cfc0, event=0x7fffa7a3ca70) at kernel/qapplication_x11.cpp:3598 #26 0x00007f0ca69cb2a2 in x11EventSourceDispatch (s=0xb80000, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #27 0x00007f0c9dfa058d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x00007f0c9dfa0d88 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x00007f0c9dfa0f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x00007f0ca77fb50f in QEventDispatcherGlib::processEvents (this=0xb21120, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #31 0x00007f0ca69caf2e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #32 0x00007f0ca77cfa22 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #33 0x00007f0ca77cfc1f in QEventLoop::exec (this=0x7fffa7a3ce40, flags=...) at kernel/qeventloop.cpp:201 #34 0x00007f0ca77d3de7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #35 0x000000000049407d in ?? () #36 0x00007f0ca5c7223d in __libc_start_main () from /lib64/libc.so.6 #37 0x0000000000495855 in _start () Possible duplicates by query: bug 287082, bug 286641, bug 285941, bug 284626, bug 284447. Reported using DrKonqi
It crash in KDE not digiKam. Can you run digiKam in a console through GDB : http://www.digikam.org/drupal/contrib Also, try with digiKam 2.3.0 or 2.4.0... Gilles Caulier
New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles caulier
Created attachment 93370 [details] attachment-23004-0.html I no longer use Linux neither digikam. Sorry