Application: digikam (2.5.0) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.1 Operating System: Linux 3.2.0-27-generic-pae i686 Distribution: Ubuntu 12.04 LTS -- Information about the crash: digikam crashed after adding a lot of pictures from all harddisks The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xaef3c8c0 (LWP 6411))] Thread 4 (Thread 0xabfffb40 (LWP 6413)): #0 0xb31d4118 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb31d4201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb4c4b8e7 in QEventDispatcherGlib::processEvents (this=0xab600468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #3 0xb4c1750d in QEventLoop::processEvents (this=0xabfff0c0, flags=...) at kernel/qeventloop.cpp:149 #4 0xb4c177a9 in QEventLoop::exec (this=0xabfff0c0, flags=...) at kernel/qeventloop.cpp:204 #5 0xb4b0094c in QThread::exec (this=0x9d890f0) at thread/qthread.cpp:501 #6 0xb4bf4b5d in QInotifyFileSystemWatcherEngine::run (this=0x9d890f0) at io/qfilesystemwatcher_inotify.cpp:248 #7 0xb4b03de0 in QThreadPrivate::start (arg=0x9d890f0) at thread/qthread_unix.cpp:298 #8 0xb357bd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #9 0xb4831ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 3 (Thread 0xab5ffb40 (LWP 6420)): #0 0xb77ba424 in __kernel_vsyscall () #1 0xb357f96b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0xb483f3dc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb4b04350 in wait (time=4294967295, this=0xa1affa8) at thread/qwaitcondition_unix.cpp:86 #4 QWaitCondition::wait (this=0xa1afde8, mutex=0xa1afde4, time=4294967295) at thread/qwaitcondition_unix.cpp:158 #5 0xb6abbb2c in Digikam::ParkingThread::run (this=0xa1afdd8) at /build/buildd/digikam-2.5.0/core/libs/threads/threadmanager.cpp:119 #6 0xb4b03de0 in QThreadPrivate::start (arg=0xa1afdd8) at thread/qthread_unix.cpp:298 #7 0xb357bd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #8 0xb4831ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xa5e47b40 (LWP 6421)): #0 0xb77ba424 in __kernel_vsyscall () #1 0xb4823380 in poll () from /lib/i386-linux-gnu/libc.so.6 #2 0xb31e1a7b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb31d40ae in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb31d4201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb4c4b8e7 in QEventDispatcherGlib::processEvents (this=0xa2b9078, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0xb4c1750d in QEventLoop::processEvents (this=0xa5e470c0, flags=...) at kernel/qeventloop.cpp:149 #7 0xb4c177a9 in QEventLoop::exec (this=0xa5e470c0, flags=...) at kernel/qeventloop.cpp:204 #8 0xb4b0094c in QThread::exec (this=0xa2b8d20) at thread/qthread.cpp:501 #9 0xb4bf4b5d in QInotifyFileSystemWatcherEngine::run (this=0xa2b8d20) at io/qfilesystemwatcher_inotify.cpp:248 #10 0xb4b03de0 in QThreadPrivate::start (arg=0xa2b8d20) at thread/qthread_unix.cpp:298 #11 0xb357bd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #12 0xb4831ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xaef3c8c0 (LWP 6411)): [KCrash Handler] #7 0x080ffb7d in Digikam::Setup::okClicked (this=0xc832678) at /build/buildd/digikam-2.5.0/core/utilities/setup/setup.cpp:468 #8 0xb5c4ca00 in qt_static_metacall (_a=0xbfe95f18, _id=33, _o=0xc832678, _c=<optimized out>) at ./kdialog.moc:167 #9 KDialog::qt_static_metacall (_o=0xc832678, _c=QMetaObject::InvokeMetaMethod, _id=33, _a=0xbfe95f18) at ./kdialog.moc:127 #10 0xb4c2f6b1 in QMetaObject::activate (sender=0xcb4c154, m=0xb4d74e58, local_signal_index=0, argv=0xbfe95f18) at kernel/qobject.cpp:3547 #11 0xb4c36da5 in QSignalMapper::mapped (this=0xcb4c154, _t1=4) at .moc/release-shared/moc_qsignalmapper.cpp:115 #12 0xb4c36ef2 in QSignalMapper::map (this=0xcb4c154, sender=0xc791400) at kernel/qsignalmapper.cpp:266 #13 0xb4c370ae in QSignalMapper::map (this=0xcb4c154) at kernel/qsignalmapper.cpp:257 #14 0xb4c37190 in qt_static_metacall (_a=0xbfe96098, _id=4, _o=0xcb4c154, _c=<optimized out>) at .moc/release-shared/moc_qsignalmapper.cpp:64 #15 QSignalMapper::qt_static_metacall (_o=0xcb4c154, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfe96098) at .moc/release-shared/moc_qsignalmapper.cpp:54 #16 0xb4c2f6b1 in QMetaObject::activate (sender=0xc791400, m=0x8547020, local_signal_index=2, argv=0xbfe96098) at kernel/qobject.cpp:3547 #17 0xb58bd97d in QAbstractButton::clicked (this=0xc791400, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:220 #18 0xb55b162d in QAbstractButtonPrivate::emitClicked (this=0xcb7c0c8) at widgets/qabstractbutton.cpp:548 #19 0xb55b2c9b in QAbstractButtonPrivate::click (this=0xcb7c0c8) at widgets/qabstractbutton.cpp:541 #20 0xb55b2f56 in QAbstractButton::mouseReleaseEvent (this=0xc791400, e=0xbfe96764) at widgets/qabstractbutton.cpp:1123 #21 0xb51e01ac in QWidget::event (this=0xc791400, event=0xbfe96764) at kernel/qwidget.cpp:8362 #22 0xb55b21f9 in QAbstractButton::event (this=0xc791400, e=0xbfe96764) at widgets/qabstractbutton.cpp:1082 #23 0xb5655768 in QPushButton::event (this=0xc791400, e=0xbfe96764) at widgets/qpushbutton.cpp:683 #24 0xb5185ed4 in notify_helper (e=0xbfe96764, receiver=0xc791400, this=0x9c59da8) at kernel/qapplication.cpp:4559 #25 QApplicationPrivate::notify_helper (this=0x9c59da8, receiver=0xc791400, e=0xbfe96764) at kernel/qapplication.cpp:4531 #26 0xb518c024 in QApplication::notify (this=0x9c59da8, receiver=0xc791400, e=0xbfe96764) at kernel/qapplication.cpp:4102 #27 0xb5d0b401 in KApplication::notify (this=0xbfe981c0, receiver=0xc791400, event=0xbfe96764) at ../../kdeui/kernel/kapplication.cpp:311 #28 0xb4c1897e in QCoreApplication::notifyInternal (this=0xbfe981c0, receiver=0xc791400, event=0xbfe96764) at kernel/qcoreapplication.cpp:876 #29 0xb5186e95 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #30 QApplicationPrivate::sendMouseEvent (receiver=0xc791400, event=0xbfe96764, alienWidget=0xc791400, nativeWidget=0xcbd4620, buttonDown=0xb5b1acf4, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3170 #31 0xb5213074 in QETWidget::translateMouseEvent (this=0xcbd4620, event=0xbfe96c1c) at kernel/qapplication_x11.cpp:4617 #32 0xb5211c0d in QApplication::x11ProcessEvent (this=0xbfe981c0, event=0xbfe96c1c) at kernel/qapplication_x11.cpp:3732 #33 0xb523eeac in x11EventSourceDispatch (s=0x9c58728, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #34 0xb31d3d86 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #35 0xb31d4125 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #36 0xb31d4201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #37 0xb4c4b887 in QEventDispatcherGlib::processEvents (this=0x9c13100, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #38 0xb523eaaa in QGuiEventDispatcherGlib::processEvents (this=0x9c13100, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #39 0xb4c1750d in QEventLoop::processEvents (this=0xbfe96f10, flags=...) at kernel/qeventloop.cpp:149 #40 0xb4c177a9 in QEventLoop::exec (this=0xbfe96f10, flags=...) at kernel/qeventloop.cpp:204 #41 0xb56d80d9 in QDialog::exec (this=0xc832678) at dialogs/qdialog.cpp:554 #42 0x08100103 in Digikam::Setup::exec (parent=0x9e1b2d8, page=Digikam::Setup::LastPageUsed) at /build/buildd/digikam-2.5.0/core/utilities/setup/setup.cpp:412 #43 0x081a7117 in Digikam::DigikamApp::setup (this=0x9e1b2d8) at /build/buildd/digikam-2.5.0/core/digikam/main/digikamapp.cpp:2495 #44 0x081b6ebd in Digikam::DigikamApp::qt_static_metacall (_o=0x9e1b2d8, _c=QMetaObject::InvokeMetaMethod, _id=37, _a=0xbfe970b8) at /build/buildd/digikam-2.5.0/obj-i686-linux-gnu/core/digikam/digikamapp.moc:231 #45 0xb4c2f6b1 in QMetaObject::activate (sender=0xae9b518, m=0x85470d8, local_signal_index=1, argv=0xbfe970b8) at kernel/qobject.cpp:3547 #46 0xb517e9bd in QAction::triggered (this=0xae9b518, _t1=false) at .moc/release-shared/moc_qaction.cpp:277 #47 0xb517ec5b in QAction::activate (this=0xae9b518, event=QAction::Trigger) at kernel/qaction.cpp:1257 #48 0xb5640453 in QMenuPrivate::activateCausedStack (this=0xb0f6ff0, causedStack=..., action=0xae9b518, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1028 #49 0xb564732f in QMenuPrivate::activateAction (this=0xb0f6ff0, action=0xae9b518, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1120 #50 0xb564a015 in QMenu::mouseReleaseEvent (this=0xac4bde8, e=0xbfe978f4) at widgets/qmenu.cpp:2360 #51 0xb5de970c in KMenu::mouseReleaseEvent (this=0xac4bde8, e=0xbfe978f4) at ../../kdeui/widgets/kmenu.cpp:464 #52 0xb51e01ac in QWidget::event (this=0xac4bde8, event=0xbfe978f4) at kernel/qwidget.cpp:8362 #53 0xb5648a9c in QMenu::event (this=0xac4bde8, e=0xbfe978f4) at widgets/qmenu.cpp:2469 #54 0xb5185ed4 in notify_helper (e=0xbfe978f4, receiver=0xac4bde8, this=0x9c59da8) at kernel/qapplication.cpp:4559 #55 QApplicationPrivate::notify_helper (this=0x9c59da8, receiver=0xac4bde8, e=0xbfe978f4) at kernel/qapplication.cpp:4531 #56 0xb518c024 in QApplication::notify (this=0x9c59da8, receiver=0xac4bde8, e=0xbfe978f4) at kernel/qapplication.cpp:4102 #57 0xb5d0b401 in KApplication::notify (this=0xbfe981c0, receiver=0xac4bde8, event=0xbfe978f4) at ../../kdeui/kernel/kapplication.cpp:311 #58 0xb4c1897e in QCoreApplication::notifyInternal (this=0xbfe981c0, receiver=0xac4bde8, event=0xbfe978f4) at kernel/qcoreapplication.cpp:876 #59 0xb5186e95 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #60 QApplicationPrivate::sendMouseEvent (receiver=0xac4bde8, event=0xbfe978f4, alienWidget=0x0, nativeWidget=0xac4bde8, buttonDown=0xb5b1acf4, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3170 #61 0xb52137d2 in QETWidget::translateMouseEvent (this=0xac4bde8, event=0xbfe97dac) at kernel/qapplication_x11.cpp:4551 #62 0xb5211c0d in QApplication::x11ProcessEvent (this=0xbfe981c0, event=0xbfe97dac) at kernel/qapplication_x11.cpp:3732 #63 0xb523eeac in x11EventSourceDispatch (s=0x9c58728, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #64 0xb31d3d86 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #65 0xb31d4125 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #66 0xb31d4201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #67 0xb4c4b887 in QEventDispatcherGlib::processEvents (this=0x9c13100, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #68 0xb523eaaa in QGuiEventDispatcherGlib::processEvents (this=0x9c13100, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #69 0xb4c1750d in QEventLoop::processEvents (this=0xbfe980a4, flags=...) at kernel/qeventloop.cpp:149 #70 0xb4c177a9 in QEventLoop::exec (this=0xbfe980a4, flags=...) at kernel/qeventloop.cpp:204 #71 0xb4c1ceba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #72 0xb5183a74 in QApplication::exec () at kernel/qapplication.cpp:3820 #73 0x080b69e4 in main (argc=228187184, argv=0xda4f2b8) at /build/buildd/digikam-2.5.0/core/digikam/main/main.cpp:232 Possible duplicates by query: bug 286641. Reported using DrKonqi
Created attachment 73031 [details] attachment-2769-0.html It crash in setup dialog. Why ? Which settings you use ? Please attach your config file ~/.kde4/share/config/digikamrc Gilles Caulier
i just added whole hdd ( /media/ter ) , after which digikam no answer or crashed. 2012/8/5 Gilles Caulier <caulier.gilles@gmail.com> > https://bugs.kde.org/show_bug.cgi?id=304603 > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |caulier.gilles@gmail.com > Component|general |setup > > --- Comment #1 from Gilles Caulier <caulier.gilles@gmail.com> --- > It crash in setup dialog. Why ? > > Which settings you use ? Please attach your config file > ~/.kde4/share/config/digikamrc > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. >
Created attachment 73032 [details] attachment-2769-1.dat
Created attachment 73033 [details] digikamrc
In 2.5.0, line 468 is d->albumViewPage->applySettings(); one after the collections page applying. Do you start digikam and then the Setup, or is the the first-run wizard? Does a collection scan dialog appear? Are the collection really added, that is, when you restart digikam you have your pictures? Still reproducible with recent versions, preferable 3.0?
digiKam 3.5.0 is out. Can you give a fresh feedback about your report ? Crash still reproducible ? Thanks in advance 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
digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance.
This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier