Application that crashed: digikam Version of the application: 0.10.0 KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) Qt Version: 4.5.0 Operating System: Linux 2.6.30-020630-generic i686 Distribution: Ubuntu 9.04 What I was doing when the application crashed: I've the DIGIKAM 1.00 BETA 1 VERSION ! -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault [Current thread is 0 (LWP 4725)] Thread 2 (Thread 0xb207eb90 (LWP 4726)): [KCrash Handler] #6 0xb7028116 in Digikam::CollectionScanner::setSignalsEnabled (this=0x0, on=true) at /home/dany/Download/digikam-1.0.0-beta1/libs/database/collectionscanner.cpp:136 #7 0x0828e56e in ?? () #8 0xb708fc63 in Digikam::SchemaUpdater::update (this=0xb207e250) at /home/dany/Download/digikam-1.0.0-beta1/libs/database/schemaupdater.cpp:97 #9 0xb704248b in Digikam::DatabaseBackend::initSchema (this=0x8bbcc08, updater=0xb207e250) at /home/dany/Download/digikam-1.0.0-beta1/libs/database/databasebackend.cpp:307 #10 0xb703d776 in Digikam::DatabaseAccess::checkReadyForUse (observer=0x8bbcf88) at /home/dany/Download/digikam-1.0.0-beta1/libs/database/databaseaccess.cpp:245 #11 0x0828f16e in ?? () #12 0xb56e896e in QThreadPrivate::start (arg=0x8bbcf80) at thread/qthread_unix.cpp:189 #13 0xb53f74ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #14 0xb54ee49e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb37a5700 (LWP 4725)): #0 0xb8092430 in __kernel_vsyscall () #1 0xb53fb0e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb54fd2ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0xb56e99b2 in QWaitCondition::wait (this=0x8bbfba0, mutex=0x8bbfb8c, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #4 0xb56e8b13 in QThread::wait (this=0x8bbcf80, time=4294967295) at thread/qthread_unix.cpp:485 #5 0x0828ef1e in ?? () #6 0x08292671 in ?? () #7 0x0829281a in ?? () #8 0xb5438bb9 in exit () from /lib/tls/i686/cmov/libc.so.6 #9 0xb5d2021b in qt_xio_errhandler () at kernel/qapplication_x11.cpp:707 #10 0xb68e183a in KApplication::xioErrhandler (this=0xbfe61aa4, dpy=0x8ac3408) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kapplication.cpp:408 #11 0xb68e1876 in kde_xio_errhandler (dpy=0x8ac3408) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kapplication.cpp:125 #12 0xb5285f22 in _XIOError () from /usr/lib/libX11.so.6 #13 0xb528d743 in ?? () from /usr/lib/libX11.so.6 #14 0xb528e0e5 in _XEventsQueued () from /usr/lib/libX11.so.6 #15 0xb52767af in XEventsQueued () from /usr/lib/libX11.so.6 #16 0xb5d5d52d in x11EventSourceCheck (s=0x8aad3f8) at kernel/qguieventdispatcher_glib.cpp:87 #17 0xb3c366f6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #18 0xb3c36fdd in ?? () from /usr/lib/libglib-2.0.so.0 #19 0xb3c37268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #20 0xb5808438 in QEventDispatcherGlib::processEvents (this=0x8aaa658, flags={i = -1075439656}) at kernel/qeventdispatcher_glib.cpp:323 #21 0xb5d5d365 in QGuiEventDispatcherGlib::processEvents (this=0x8aaa658, flags={i = -1075439608}) at kernel/qguieventdispatcher_glib.cpp:202 #22 0xb57db06a in QEventLoop::processEvents (this=0x8b3c7a0, flags={i = -1075439544}) at kernel/qeventloop.cpp:149 #23 0xb57db4aa in QEventLoop::exec (this=0x8b3c7a0, flags={i = -1075439492}) at kernel/qeventloop.cpp:200 #24 0x0828ee64 in ?? () #25 0x0821872c in ?? () #26 0x082b4b70 in ?? () #27 0xb5420775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #28 0x0808ddc1 in _start () Reported using DrKonqi
Seems the backtrace is corrupted. There is no codepath leading from schemaupdater.cpp:97 (calling scancontroller.cpp:591) to setSignalsEnabled (called from scancontroller.cpp:493, called from scancontroller.cpp:473). Try running digikam under gdb, often this gives a more correct backtrace.
*** Bug 204071 has been marked as a duplicate of this bug. ***
Could this be fixed? All related reports seem to be marked as FIXED though.
Closing now. Reopen if new info comes up.