Application that crashed: kontact Version of the application: 4.3.0 pre KDE Version: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 125" Qt Version: 4.5.1 Operating System: Linux 2.6.27.21-0.1-default x86_64 Distribution: "openSUSE 11.1 (x86_64)" What I was doing when the application crashed: Kontact crashed on startup -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 0x00007f8b630f3c1a in Kontact::MainWindow::activatePluginModule() () from /usr/lib64/libkontactprivate.so.4 #6 0x00000000004036f2 in _start ()
*** Bug 193525 has been marked as a duplicate of this bug. ***
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You need to install the "kdepim4-debuginfo" package. Thanks
*** Bug 193025 has been marked as a duplicate of this bug. ***
*** Bug 196026 has been marked as a duplicate of this bug. ***
*** Bug 196036 has been marked as a duplicate of this bug. ***
*** Bug 196233 has been marked as a duplicate of this bug. ***
*** Bug 196423 has been marked as a duplicate of this bug. ***
*** Bug 196625 has been marked as a duplicate of this bug. ***
Some additional information: 1.) The crash is 100% reproduceable for me under conditions of 2.) It happens exactly every second (!) time kontact is started. That means: after closing kontact the first attempt to start crashes, the second one succeeds. 2.) The crash seems to occur only, if akregator has been started inside kontact. 3.) It appears to me that starting something like "kmail --composer" directly instead of kontact is not possible, only starting the kontact shell seems to fix the problem to allow success with the second try. ----- Backtrace using kdepim4-4.2.90 @ opensuse-11.1 @ x86-64: ----- Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f68478e8750 (LWP 12830))] Thread 3 (Thread 0x7f682aada950 (LWP 13179)): #0 0x00007f6842c8dfdd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f6842efeeb7 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x00007f6842ef4a89 in ?? () from /usr/lib64/libQtCore.so.4 #3 0x00007f6842efdf22 in ?? () from /usr/lib64/libQtCore.so.4 #4 0x00007f6842c8a070 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f684113c10d in clone () from /lib64/libc.so.6 #6 0x0000000000000000 in ?? () Thread 2 (Thread 0x7f682773e950 (LWP 13199)): #0 0x00007f6842c8dfdd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f6842efeeb7 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x00007f6842ef4a89 in ?? () from /usr/lib64/libQtCore.so.4 #3 0x00007f6842efdf22 in ?? () from /usr/lib64/libQtCore.so.4 #4 0x00007f6842c8a070 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f684113c10d in clone () from /lib64/libc.so.6 #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f68478e8750 (LWP 12830)): [KCrash Handler] #5 Kontact::MainWindow::activatePluginModule (this=0x63f920) at /usr/src/debug/kdepim-4.2.90/kontact/src/mainwindow.cpp:300 #6 0x00000000004036f2 in KontactApp::newInstance (this=0x7fff4f955020) at /usr/src/debug/kdepim-4.2.90/kontact/src/main.cpp:147 #7 0x00007f6843e28df6 in ?? () from /usr/lib64/libkdeui.so.5 #8 0x00007f6843e28e82 in ?? () from /usr/lib64/libkdeui.so.5 #9 0x00007f6843301394 in ?? () from /usr/lib64/libQtDBus.so.4 #10 0x00007f6843302408 in ?? () from /usr/lib64/libQtDBus.so.4 #11 0x00007f6843302a31 in ?? () from /usr/lib64/libQtDBus.so.4 #12 0x00007f6843302d48 in ?? () from /usr/lib64/libQtDBus.so.4 #13 0x00007f6842ff72b8 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #14 0x00007f6841cdff2a in QApplication::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #15 0x00007f6841cda78d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #16 0x00007f6841ce2a2a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #17 0x00007f6843e2204b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #18 0x00007f6842fe715c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #19 0x00007f6842fe7dda in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #20 0x00007f6843010c13 in ?? () from /usr/lib64/libQtCore.so.4 #21 0x00007f683c8910fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #22 0x00007f683c8948cd in ?? () from /usr/lib64/libglib-2.0.so.0 #23 0x00007f683c894a8b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #24 0x00007f684301089f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #25 0x00007f6841d71b0f in ?? () from /usr/lib64/libQtGui.so.4 #26 0x00007f6842fe59f2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #27 0x00007f6842fe5dbd in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #28 0x00007f6842fe80a4 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #29 0x0000000000404995 in main (argc=1, argv=0x7fff4f955708) at /usr/src/debug/kdepim-4.2.90/kontact/src/main.cpp:218
*** Bug 197110 has been marked as a duplicate of this bug. ***
switched from akregator to kmail in kontact. 4.2.90 qt 4.5.1 4.2.90 is running for quite some time here, heavily using it but that was the first time i got that backtrace, no idea how to reproduce. Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xb779202c in Kontact::Plugin::identifier (this=0x900806e) at /usr/include/qt4/QtCore/qstring.h:711 #7 0xb77abff9 in Kontact::MainWindow::activatePluginModule (this=0x9028dc8) at /build/buildd/kdepim-4.2.90/kontact/src/mainwindow.cpp:300 #8 0xb77ac0a4 in Kontact::MainWindow::setActivePluginModule (this=0x9028dc8, module=@0xbf81bbd4) at /build/buildd/kdepim-4.2.90/kontact/src/mainwindow.cpp:278 #9 0x0804ac57 in KontactApp::newInstance (this=0xbf81c738) at /build/buildd/kdepim-4.2.90/kontact/src/main.cpp:147 #10 0xb6c4b516 in KUniqueApplicationAdaptor::newInstance (this=0x90888e8, asn_id=@0xa631d18, args=@0x9f49f88) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kuniqueapplication.cpp:454 #11 0xb6c4b5be in KUniqueApplicationAdaptor::qt_metacall (this=0x90888e8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf81be28) at /build/buildd/kde4libs-4.2.90/obj-i486-linux-gnu/kdeui/kuniqueapplication_p.moc:75 #12 0xb5c79e2a in QDBusConnectionPrivate::deliverCall (this=0x9010e68, object=0x90888e8, msg=@0xaef7558, metaTypes=@0xa014d94, slotIdx=4) at qdbusintegrator.cpp:891 #13 0xb5c7b149 in QDBusConnectionPrivate::activateCall (this=0x9010e68, object=0x90888e8, flags=337, msg=@0xaef7558) at qdbusintegrator.cpp:803 #14 0xb5c7b5b1 in QDBusConnectionPrivate::activateObject (this=0x9010e68, node=@0xaef7544, msg=@0xaef7558, pathStartPos=16) at qdbusintegrator.cpp:1375 #15 0xb5c7baaa in QDBusActivateObjectEvent::placeMetaCall (this=0xaef7518) at qdbusintegrator.cpp:1469 #16 0xb5b72150 in QObject::event (this=0xbf81c738, e=0xaef7518) at kernel/qobject.cpp:1118 #17 0xb5b6114b in QCoreApplication::event (this=0xbf81c738, e=0xaef7518) at kernel/qcoreapplication.cpp:1434 #18 0xb6025509 in QApplication::event (this=0xbf81c738, e=0xaef7518) at kernel/qapplication.cpp:2318 #19 0xb601fbcc in QApplicationPrivate::notify_helper (this=0x9019330, receiver=0xbf81c738, e=0xaef7518) at kernel/qapplication.cpp:4057 #20 0xb6027ede in QApplication::notify (this=0xbf81c738, receiver=0xbf81c738, e=0xaef7518) at kernel/qapplication.cpp:3604 #21 0xb6c43e8d in KApplication::notify (this=0xbf81c738, receiver=0xbf81c738, event=0xaef7518) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kapplication.cpp:302 #22 0xb5b617ab in QCoreApplication::notifyInternal (this=0xbf81c738, receiver=0xbf81c738, event=0xaef7518) at kernel/qcoreapplication.cpp:610 #23 0xb5b62405 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8ff8c08) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #24 0xb5b625fd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #25 0xb5b8d58f in postEventSourceDispatch (s=0x901b320) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #26 0xb4c36b88 in IA__g_main_context_dispatch (context=0x901b298) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814 #27 0xb4c3a0eb in g_main_context_iterate (context=0x901b298, block=1, dispatch=1, self=0x90180f8) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448 #28 0xb4c3a268 in IA__g_main_context_iteration (context=0x901b298, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511 #29 0xb5b8d1d8 in QEventDispatcherGlib::processEvents (this=0x90153a8, flags={i = -1082014200}) at kernel/qeventdispatcher_glib.cpp:324 #30 0xb60c1765 in QGuiEventDispatcherGlib::processEvents (this=0x90153a8, flags={i = -1082014152}) at kernel/qguieventdispatcher_glib.cpp:202 #31 0xb5b5fdda in QEventLoop::processEvents (this=0xbf81c6b0, flags={i = -1082014088}) at kernel/qeventloop.cpp:149 #32 0xb5b6021a in QEventLoop::exec (this=0xbf81c6b0, flags={i = -1082014024}) at kernel/qeventloop.cpp:200 #33 0xb5b626c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #34 0xb601fa47 in QApplication::exec () at kernel/qapplication.cpp:3526 #35 0x0804bfef in main (argc=1, argv=0xbf81ca34) at /build/buildd/kdepim-4.2.90/kontact/src/main.cpp:218
Quite a few duplicates and still UNCONFIRMED? Well, whatever.... here's my backtrace if that's of any significance: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xb78da09c in Kontact::Plugin::identifier (this=0x83081e8) at /usr/include/QtCore/qstring.h:711 #7 0xb78f4069 in Kontact::MainWindow::activatePluginModule (this=0x8086e10) at /usr/src/debug/kdepim-4.2.90/kontact/src/mainwindow.cpp:300 #8 0xb78f4114 in Kontact::MainWindow::setActivePluginModule (this=0x8086e10, module=@0xbf89fac4) at /usr/src/debug/kdepim-4.2.90/kontact/src/mainwindow.cpp:278 #9 0x0804acb7 in KontactApp::newInstance (this=0xbf8a0648) at /usr/src/debug/kdepim-4.2.90/kontact/src/main.cpp:147 #10 0xb6cbf066 in KUniqueApplicationAdaptor::newInstance (this=0x80bc500, asn_id=@0x8dfd890, args=@0x8f091e0) at /usr/src/debug/kdelibs-4.2.90/kdeui/kernel/kuniqueapplication.cpp:454 #11 0xb6cbf10e in KUniqueApplicationAdaptor::qt_metacall (this=0x80bc500, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf89fd2c) at /usr/src/debug/kdelibs-4.2.90/build/kdeui/kuniqueapplication_p.moc:75 #12 0xb67ed873 in QDBusConnectionPrivate::deliverCall (this=0x806b5c8, object=0x80bc500, msg=@0x82aba60, metaTypes=@0x8ead59c, slotIdx=4) at qdbusintegrator.cpp:891 #13 0xb67ee939 in QDBusConnectionPrivate::activateCall (this=0x806b5c8, object=0x80bc500, flags=337, msg=@0x82aba60) at qdbusintegrator.cpp:803 #14 0xb67eeda1 in QDBusConnectionPrivate::activateObject (this=0x806b5c8, node=@0x82aba4c, msg=@0x82aba60, pathStartPos=16) at qdbusintegrator.cpp:1370 #15 0xb67ef29a in QDBusActivateObjectEvent::placeMetaCall (this=0x82aba20) at qdbusintegrator.cpp:1464 #16 0xb66e1970 in QObject::event (this=0xbf8a0648, e=0x82aba20) at kernel/qobject.cpp:1111 #17 0xb66d0afb in QCoreApplication::event (this=0xbf8a0648, e=0x82aba20) at kernel/qcoreapplication.cpp:1434 #18 0xb5bad119 in QApplication::event (this=0xbf8a0648, e=0x82aba20) at kernel/qapplication.cpp:2317 #19 0xb5ba77fc in QApplicationPrivate::notify_helper (this=0x8080f20, receiver=0xbf8a0648, e=0x82aba20) at kernel/qapplication.cpp:4056 #20 0xb5bafaee in QApplication::notify (this=0xbf8a0648, receiver=0xbf8a0648, e=0x82aba20) at kernel/qapplication.cpp:3603 #21 0xb6cb7b9d in KApplication::notify (this=0xbf8a0648, receiver=0xbf8a0648, event=0x82aba20) at /usr/src/debug/kdelibs-4.2.90/kdeui/kernel/kapplication.cpp:302 #22 0xb66d116b in QCoreApplication::notifyInternal (this=0xbf8a0648, receiver=0xbf8a0648, event=0x82aba20) at kernel/qcoreapplication.cpp:610 #23 0xb66d1db5 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8053b30) at kernel/qcoreapplication.h:213 #24 0xb66d1fad in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #25 0xb66fcc8f in postEventSourceDispatch (s=0x8073cc0) at kernel/qcoreapplication.h:218 #26 0xb4e6cea8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #27 0xb4e7041b in ?? () from /usr/lib/libglib-2.0.so.0 #28 0xb4e70598 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #29 0xb66fc8d8 in QEventDispatcherGlib::processEvents (this=0x8080108, flags={i = -1081473768}) at kernel/qeventdispatcher_glib.cpp:327 #30 0xb5c47cc5 in QGuiEventDispatcherGlib::processEvents (this=0x8080108, flags={i = -1081473720}) at kernel/qguieventdispatcher_glib.cpp:202 #31 0xb66cf78a in QEventLoop::processEvents (this=0xbf8a05c0, flags={i = -1081473656}) at kernel/qeventloop.cpp:149 #32 0xb66cfbd2 in QEventLoop::exec (this=0xbf8a05c0, flags={i = -1081473592}) at kernel/qeventloop.cpp:201 #33 0xb66d2079 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #34 0xb5ba7677 in QApplication::exec () at kernel/qapplication.cpp:3525 #35 0x0804c04f in main (argc=1, argv=0xbf8a0944) at /usr/src/debug/kdepim-4.2.90/kontact/src/main.cpp:218
*** Bug 198871 has been marked as a duplicate of this bug. ***
*** Bug 199796 has been marked as a duplicate of this bug. ***
*** Bug 200838 has been marked as a duplicate of this bug. ***
*** Bug 202677 has been marked as a duplicate of this bug. ***
*** Bug 202846 has been marked as a duplicate of this bug. ***
The bug is still available in KDE 4.3.0, why is it still UNCONFIRMED? Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 Kontact::MainWindow::activatePluginModule (this=0xbe3c00) at /build/buildd/kdepim-4.3.0/kontact/src/mainwindow.cpp:303 #6 0x00000000004036a2 in KontactApp::newInstance (this=0x7fffc3f5b180) at /build/buildd/kdepim-4.3.0/kontact/src/main.cpp:147 #7 0x00007f7bb8428656 in KUniqueApplicationAdaptor::newInstance (this=0xb2f580, asn_id=<value optimized out>, args=@0x21acfd0) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kuniqueapplication.cpp:459 #8 0x00007f7bb84286e2 in KUniqueApplicationAdaptor::qt_metacall (this=0xb2f580, _c=QMetaObject::InvokeMetaMethod, _id=-1007313249, _a=0x7fffc3f5a420) at /build/buildd/kde4libs-4.3.0/obj-x86_64-linux-gnu/kdeui/kuniqueapplication_p.moc:75 #9 0x00007f7bb67b8453 in QDBusConnectionPrivate::deliverCall (this=0xa6c790, object=0xb2f580, msg=@0x22ee2b0, metaTypes=@0xb9d840, slotIdx=4) at qdbusintegrator.cpp:891 #10 0x00007f7bb67b9778 in QDBusConnectionPrivate::activateCall (this=0xa6c790, object=0xb2f580, flags=337, msg=@0x22ee2b0) at qdbusintegrator.cpp:803 #11 0x00007f7bb67b9da1 in QDBusConnectionPrivate::activateObject (this=0xa6c790, node=@0x22ee288, msg=@0x22ee2b0, pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1347 #12 0x00007f7bb67ba0b8 in QDBusActivateObjectEvent::placeMetaCall (this=0x22ee240) at qdbusintegrator.cpp:1464 #13 0x00007f7bb64ae5d8 in QObject::event (this=0x7fffc3f5b180, e=0x22ee240) at kernel/qobject.cpp:1111 #14 0x00007f7bb70226ca in QApplication::event (this=0x7fffc3f5b180, e=0x22ee240) at kernel/qapplication.cpp:2317 #15 0x00007f7bb701cf4d in QApplicationPrivate::notify_helper (this=0xa815b0, receiver=0x7fffc3f5b180, e=0x22ee240) at kernel/qapplication.cpp:4056 #16 0x00007f7bb702518a in QApplication::notify (this=0x7fffc3f5b180, receiver=0x7fffc3f5b180, e=0x22ee240) at kernel/qapplication.cpp:4021 #17 0x00007f7bb842171b in KApplication::notify (this=0x7fffc3f5b180, receiver=0x7fffc3f5b180, event=0x22ee240) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302 #18 0x00007f7bb649e6ac in QCoreApplication::notifyInternal (this=0x7fffc3f5b180, receiver=0x7fffc3f5b180, event=0x22ee240) at kernel/qcoreapplication.cpp:610 #19 0x00007f7bb649f31a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xa4f850) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #20 0x00007f7bb64c7e03 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #21 0x00007f7bafbef20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #22 0x00007f7bafbf28e0 in ?? () from /usr/lib/libglib-2.0.so.0 #23 0x00007f7bafbf2a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #24 0x00007f7bb64c7a8f in QEventDispatcherGlib::processEvents (this=0xa4f0a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #25 0x00007f7bb70b5bdf in QGuiEventDispatcherGlib::processEvents (this=0xbe3c00, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #26 0x00007f7bb649cf42 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1007308640}) at kernel/qeventloop.cpp:149 #27 0x00007f7bb649d314 in QEventLoop::exec (this=0x7fffc3f5b0e0, flags={i = -1007308560}) at kernel/qeventloop.cpp:201 #28 0x00007f7bb649f5e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #29 0x0000000000404945 in main (argc=1, argv=0x7fffc3f5b868) at /build/buildd/kdepim-4.3.0/kontact/src/main.cpp:218
right, kontact 4.3.0 still crashes on every second startup (see comment #9)
*** Bug 203909 has been marked as a duplicate of this bug. ***
*** Bug 204951 has been marked as a duplicate of this bug. ***
*** Bug 205419 has been marked as a duplicate of this bug. ***
*** Bug 205668 has been marked as a duplicate of this bug. ***
still exist in 4.3.1
*** Bug 206504 has been marked as a duplicate of this bug. ***
*** Bug 207878 has been marked as a duplicate of this bug. ***
*** Bug 207960 has been marked as a duplicate of this bug. ***
*** Bug 207945 has been marked as a duplicate of this bug. ***
*** Bug 207974 has been marked as a duplicate of this bug. ***
*** Bug 209637 has been marked as a duplicate of this bug. ***
*** Bug 209750 has been marked as a duplicate of this bug. ***
*** Bug 210528 has been marked as a duplicate of this bug. ***
*** Bug 211505 has been marked as a duplicate of this bug. ***
*** Bug 212127 has been marked as a duplicate of this bug. ***
*** Bug 193087 has been marked as a duplicate of this bug. ***
*** Bug 212236 has been marked as a duplicate of this bug. ***
How many dupes have to be filed before anyone works on fixing this?
*** Bug 212385 has been marked as a duplicate of this bug. ***
From bug 212385: --- It seems I could solve this issue here. Kadressbook has had an Akonadi-Resource wich points to my Adressbookfile. As I changed this at KDE-Resources in Systemsettings to "file-Resource" pointing to the same file. This had to effects: - Kontact doesn't need 20minutes to start anymore, - Kontact closes and starts without segfault
*** Bug 212937 has been marked as a duplicate of this bug. ***
*** Bug 212985 has been marked as a duplicate of this bug. ***
*** Bug 213012 has been marked as a duplicate of this bug. ***
*** Bug 213219 has been marked as a duplicate of this bug. ***
*** Bug 213323 has been marked as a duplicate of this bug. ***
*** Bug 213525 has been marked as a duplicate of this bug. ***
*** Bug 215184 has been marked as a duplicate of this bug. ***
*** Bug 216275 has been marked as a duplicate of this bug. ***
*** Bug 215767 has been marked as a duplicate of this bug. ***
*** Bug 216513 has been marked as a duplicate of this bug. ***
*** Bug 216723 has been marked as a duplicate of this bug. ***
I suffer this bug on 4.3.4. Report from KDE bug reporter http://wklej.org/id/227486/
Well, they're random crashes. At least KDE bug reporter thinks so. I see no Kontact window before he appears.
To comment #52: Why do you think it's random ? I tested again, the bug still exists in kde-4.3.4, behaves exactly as written in Comment #9. That means it is clearly reproduceable.
> 2.) It happens exactly every second (!) time kontact is started. That > means: after closing kontact the first attempt to start crashes, > the second one succeeds. I tried. First crashed but next three times it started. > 2.) The crash seems to occur only, if akregator has been started inside > kontact. Well, I haven't tried without Akregator. > 3.) It appears to me that starting something like "kmail --composer" directly > instead of kontact is not possible, only starting the kontact shell seems > to fix the problem to allow success with the second try. I can start 'kmail --composer'.
*** Bug 217939 has been marked as a duplicate of this bug. ***
I agree that it seems Akregator is responsible for this problem - wholly or partially at least. I've tried Using Kontact with mail, news, and/or Calendar and had no failures. I use Akregator alone, quite Kontact, restart, and get a crash straight away.
*** Bug 218970 has been marked as a duplicate of this bug. ***
*** Bug 218930 has been marked as a duplicate of this bug. ***
I can confirm this bug in kde 4.3.4 exactly as commented in #9 Under the system monitor I check that even if I close kontact and korganizer daemon, sometimes there is still a kontact process in memory. Whenever this happens, trying to open kontact deals with the segfault. If the kontact process ends, then there is no segfault even if it is the second time you open the application. So, maybe this is related to #39. Maybe the old kontact is trying to close and clean data, or waiting a reponse to finish closing (akonadi?) and reopening it without proper closing the old one produces the segfault.
Hi, I think I have a scenario that works 100% all time ... for me it works on a netbook (Asus Aspire One AOA 110) and on a laptop (HP HDX 18) with a mandriva 2010 up to date (kde 4.3.2) 1. Create a new user 2. Login with the new user 3. Open Kontact 4. Open Akgregator (there are some rss per default) 5. Select (click) an article (KDE Dot news for example) 6. Click on the "Complete Story" hyperlink 7. Quit Kontact with the menu file - quit Important remark: kontact (Pid) is always on list of open processes (ksysguard) 8. Start kontact ==> nothing on screen and if i want to reopen a second time kontact nothing ... Rmk: For my normal user it crash immediately on the first recall of Kontact perhaps because I download automaticaly new mails so there is another process for Kontact, thing I do not with my scenario here. 9. Click on KOrganizer Reminder Daemon in system tray ==> crash Traces: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xb781bd05 in Kontact::Plugin::part () from /usr/lib/libkontactinterfaces.so.4 #7 0xb0c26b2a in ?? () from /usr/lib/kde4/kontact_todoplugin.so #8 0xb781e78d in Kontact::UniqueAppHandler::newInstance () from /usr/lib/libkontactinterfaces.so.4 #9 0xb781e81c in Kontact::UniqueAppHandler::qt_metacall () from /usr/lib/libkontactinterfaces.so.4 #10 0xb585075a in QDBusConnectionPrivate::deliverCall (this=0x92c62c0, object=0x94d4bd0, msg=@0xa0e17b0, metaTypes=@0xbfbcaebc, slotIdx=155920120) at qdbusintegrator.cpp:891 #11 0xb5851982 in QDBusConnectionPrivate::activateCall (this=0x92c62c0, object=0x94d4bd0, flags=272, msg=@0xa0e17b0) at qdbusintegrator.cpp:796 #12 0xb5852090 in QDBusConnectionPrivate::activateObject (this=0x92c62c0, node=@0xa0e179c, msg=@0xa0e17b0, pathStartPos=26) at qdbusintegrator.cpp:1370 #13 0xb58525f8 in QDBusActivateObjectEvent::placeMetaCall (this=0xa0e1770) at qdbusintegrator.cpp:1464 #14 0xb6fa9076 in QObject::event (this=0x94d4bd0, e=0xa0e1770) at kernel/qobject.cpp:1110 #15 0xb65bf68c in QApplicationPrivate::notify_helper (this=0x92cea80, receiver=0x94d4bd0, e=0xa0e1770) at kernel/qapplication.cpp:4065 #16 0xb65c70ce in QApplication::notify (this=0xbfbcb6d4, receiver=0x94d4bd0, e=0xa0e1770) at kernel/qapplication.cpp:3605 #17 0xb74d3a21 in KApplication::notify () from /usr/lib/libkdeui.so.5 #18 0xb6f98c0e in QCoreApplication::notifyInternal (this=0xbfbcb6d4, receiver=0x94d4bd0, event=0xa0e1770) at kernel/qcoreapplication.cpp:610 #19 0xb6f998bc in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x92aebd8) at ../../src/corelib/kernel/qcoreapplication.h:213 #20 0xb6f99a7c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #21 0xb6fc4dbd in postEventSourceDispatch (s=0x92d8e88) at ../../src/corelib/kernel/qcoreapplication.h:218 #22 0xb48f2b92 in IA__g_main_context_dispatch (context=0x92d86a0) at gmain.c:1960 #23 0xb48f6468 in g_main_context_iterate (context=0x92d86a0, block=<value optimized out>, dispatch=1, self=0x92ce730) at gmain.c:2591 #24 0xb48f658e in IA__g_main_context_iteration (context=0x92d86a0, may_block=1) at gmain.c:2654 #25 0xb6fc48f1 in QEventDispatcherGlib::processEvents (this=0x92cc080, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:406 #26 0xb66614ba in QGuiEventDispatcherGlib::processEvents (this=0x92cc080, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202 #27 0xb6f9726d in QEventLoop::processEvents (this=0xbfbcb634, flags=) at kernel/qeventloop.cpp:149 #28 0xb6f976b9 in QEventLoop::exec (this=0xbfbcb634, flags={i = 0}) at kernel/qeventloop.cpp:201 #29 0xb6f99b50 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #30 0xb65bf504 in QApplication::exec () at kernel/qapplication.cpp:3525 #31 0x0804b1c6 in _start () A+ Raph
*** Bug 219341 has been marked as a duplicate of this bug. ***
I noticed a similar behaviour on KDE 4.3.4 (1) Start Kontact (2) Make sure to enter Akregator (3) Close Kontact by right-clicking the kmail tray icon -> close (4) Wait a very long time until all processes have finished (socket processes) if you then run ps aux | grep kontact you'll notice that the kontact binary is still a running process. I have to manually kill it before I can restart kontact.
I could reproduce Kontact still running after quitting it with KDE 4.3.4, but not with KDE 4.4 beta1 anymore, so I think this problem is fixed in trunk.
*** Bug 219804 has been marked as a duplicate of this bug. ***
*** Bug 219872 has been marked as a duplicate of this bug. ***
*** Bug 220295 has been marked as a duplicate of this bug. ***
This is what I got a few minutes ago -- running trunk: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xb76c210b in QString (other=<value optimized out>, this=<value optimized out>) at /usr/include/QtCore/qstring.h:714 #7 KontactInterface::Plugin::identifier (other=<value optimized out>, this=<value optimized out>) at /usr/src/debug/kdepimlibs-4.3.86svn1068163/kontactinterface/plugin.cpp:101 #8 0xb7852ac3 in Kontact::MainWindow::activateInitialPluginModule (this=0x813ac90) at /usr/src/debug/kdepim-4.3.86svn1068163/kontact/src/mainwindow.cpp:289 #9 0xb7852b75 in Kontact::MainWindow::setInitialActivePluginModule (this=0x813ac90, module=...) at /usr/src/debug/kdepim-4.3.86svn1068163/kontact/src/mainwindow.cpp:266 #10 0x0804bd50 in KontactApp::newInstance (this=0xbfff0a34) at /usr/src/debug/kdepim-4.3.86svn1068163/kontact/src/main.cpp:150 #11 0xb72d92b3 in ?? () from /usr/lib/libkdeui.so.5 #12 0xb72d9a4c in ?? () from /usr/lib/libkdeui.so.5 #13 0xb550560e in QDBusConnectionPrivate::deliverCall (this=0x806cd80, object=0x80d1a60, msg=..., metaTypes=..., slotIdx=-1073808040) at qdbusintegrator.cpp:904 #14 0xb55064ce in QDBusConnectionPrivate::activateCall (this=0x806cd80, object=0x80d1a60, flags=337, msg=...) at qdbusintegrator.cpp:816 #15 0xb5506ffe in QDBusConnectionPrivate::activateObject (this=0x806cd80, node=..., msg=..., pathStartPos=-1073807028) at qdbusintegrator.cpp:1362 #16 0xb55072c8 in QDBusActivateObjectEvent::placeMetaCall (this=0x83dcae8) at qdbusintegrator.cpp:1475 #17 0xb6d5dedf in QObject::event (this=0xbfff0a34, e=0x83dcae8) at kernel/qobject.cpp:1240 #18 0xb6d4cb6a in QCoreApplication::event (this=0xbfff0a34, e=0x83dcae8) at kernel/qcoreapplication.cpp:1533 #19 0xb62a4e78 in QApplication::event (this=0xbfff0a34, e=0x83dcae8) at kernel/qapplication.cpp:2350 #20 0xb62a068c in QApplicationPrivate::notify_helper (this=0x807d530, receiver=0xbfff0a34, e=0x83dcae8) at kernel/qapplication.cpp:4297 #21 0xb62a74d0 in QApplication::notify (this=0xbfff0a34, receiver=0xbfff0a34, e=0x83dcae8) at kernel/qapplication.cpp:4180 #22 0xb72d1641 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #23 0xb6d4d06e in QCoreApplication::notifyInternal (this=0xbfff0a34, receiver=0xbfff0a34, event=0x83dcae8) at kernel/qcoreapplication.cpp:704 #24 0xb6d4fa73 in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:215 #25 QCoreApplicationPrivate::sendPostedEvents (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.cpp:1345 #26 0xb6d4fbcc in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238 #27 0xb6d7a15d in sendPostedEvents () at kernel/qcoreapplication.h:220 #28 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:276 #29 0xb40eb4c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #30 0xb40eed98 in ?? () from /usr/lib/libglib-2.0.so.0 #31 0xb40eeebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #32 0xb6d79c41 in QEventDispatcherGlib::processEvents (this=0x8074838, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #33 0xb636081a in QGuiEventDispatcherGlib::processEvents (this=0x8074838, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #34 0xb6d4b6dd in QEventLoop::processEvents (this=0xbfff0994, flags=) at kernel/qeventloop.cpp:149 #35 0xb6d4bb29 in QEventLoop::exec (this=0xbfff0994, flags=...) at kernel/qeventloop.cpp:201 #36 0xb6d4fca0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #37 0xb62a0734 in QApplication::exec () at kernel/qapplication.cpp:3576 #38 0x0804b506 in main (argc=1, argv=0xbfff0c44) at /usr/src/debug/kdepim-4.3.86svn1068163/kontact/src/main.cpp:221
Could one of the maintainers tell us whether there is any hope of having this bug fixed? Or is it one of the problems that is just supposed to go away when the great Akonadi rewrite is finished?
*** Bug 222829 has been marked as a duplicate of this bug. ***
*** Bug 223117 has been marked as a duplicate of this bug. ***
*** Bug 223091 has been marked as a duplicate of this bug. ***
KDE 4.4 (RC1) also still has this bug.
Application that crashed: kontact Version of the application: 4.3.4 KDE Version: 4.3.4 (KDE 4.3.4) "release 2" Qt Version: 4.5.3 Operating System: Linux 2.6.31.8-0.1-default x86_64 Distribution: "openSUSE 11.2 (x86_64)" What I was doing when the application crashed: Log in to network 1 -> suspend laptop to ram -> start again -> connect to network 2 -> kmail is now not able to check mails (IMAP) -> close kontact -> start it again and it craches -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 Kontact::MainWindow::activatePluginModule (this=0x6c63e0) at /usr/src/debug/kdepim-4.3.4/kontact/src/mainwindow.cpp:303 #6 0x0000000000404792 in KontactApp::newInstance (this=0x7fffc0708bc0) at /usr/src/debug/kdepim-4.3.4/kontact/src/main.cpp:147 #7 0x00007faf33ff5c46 in KUniqueApplicationAdaptor::newInstance (this=0x6c9ff0, asn_id=<value optimized out>, args=...) at /usr/src/debug/kdelibs-4.3.4/kdeui/kernel/kuniqueapplication.cpp:459 #8 0x00007faf33ff6236 in KUniqueApplicationAdaptor::qt_metacall (this=0x6c9ff0, _c=InvokeMetaMethod, _id=9874592, _a=0x7fffc0707ef0) at /usr/src/debug/kdelibs-4.3.4/build/kdeui/kuniqueapplication_p.moc:75 #9 0x00007faf30c45b78 in ?? () from /usr/lib64/libQtDBus.so.4 #10 0x00007faf30c469b3 in ?? () from /usr/lib64/libQtDBus.so.4 #11 0x00007faf30c47237 in ?? () from /usr/lib64/libQtDBus.so.4 #12 0x00007faf30c474b8 in ?? () from /usr/lib64/libQtDBus.so.4 #13 0x00007faf336802d9 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #14 0x00007faf32b45efd in QApplication::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #15 0x00007faf32b3c2ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #16 0x00007faf32b4357e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #17 0x00007faf33feef26 in KApplication::notify (this=0x7fffc0708bc0, receiver=0x7fffc0708bc0, event=0x1a12660) at /usr/src/debug/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302 #18 0x00007faf33670ddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #19 0x00007faf336719ea in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #20 0x00007faf33699803 in ?? () from /usr/lib64/libQtCore.so.4 #21 0x00007faf2c270dde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #22 0x00007faf2c2747a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #23 0x00007faf2c2748d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #24 0x00007faf336993a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #25 0x00007faf32bcf31e in ?? () from /usr/lib64/libQtGui.so.4 #26 0x00007faf3366f712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #27 0x00007faf3366fae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #28 0x00007faf33671c99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #29 0x0000000000403f67 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.3.4/kontact/src/main.cpp:218
*** Bug 223711 has been marked as a duplicate of this bug. ***
From bug 224627: --- Remarks: - I do not use Akonadi (the Akonadi server is completely off and no Akonadi resources are added in systemconfig). - I use Groupware addressbook though (hosted on localhost). - I use Akregator inside Kontact and a couple of IMAP accounts inside KMail - Crash don't occur every second execution as some others have reported.
*** Bug 224627 has been marked as a duplicate of this bug. ***
Dario, I also do not use Akonadi under KDE 4.3.4 (I've checked and it's not running) but have been trying KDE 4.4 and avoiding Akonadi seems not to be an option. In 4.3.4, Kontact also doesn't crash for me after every second ezecution - it's after *every* execution if I use Akregator. ;-) Under 4.4 (RC2), Kontact crashes even when I don't use Akregator. I think I'll set up a new user session and see what happens with that. I've always found Kontact to be been prone to problems in configuration and data files.
Created attachment 40680 [details] New crash information added by DrKonqi Crashed on start of kontact after updating to kde 4.4 I do not use Akregator and do not even have that installed
*** Bug 226688 has been marked as a duplicate of this bug. ***
Created attachment 41747 [details] New crash information added by DrKonqi I start kontact then close it. kontact seems to remain resident. I restart kontact and receive the crash.
*** Bug 226815 has been marked as a duplicate of this bug. ***
*** Bug 228954 has been marked as a duplicate of this bug. ***
*** Bug 232683 has been marked as a duplicate of this bug. ***
*** Bug 233509 has been marked as a duplicate of this bug. ***
So this crash bug has existed for at least 6 months and has been (apparently) narrowed down to some type of interaction in Akregator. Do crash bugs not receive some type of priority in the bug-killing queue? For users, like myself, who frequently use Kontact for mail and RSS reading, this bug rears its ugly head on a daily basis. Can this crash bug be shown some love and finally fixed, please?
This bug only has 140 votes. The top 5 most hated bugs all have more than a thousand. If you want this bug to get some love, voting for it might help.
*** Bug 233723 has been marked as a duplicate of this bug. ***
*** Bug 234169 has been marked as a duplicate of this bug. ***
*** Bug 234559 has been marked as a duplicate of this bug. ***
*** Bug 235532 has been marked as a duplicate of this bug. ***
*** Bug 236196 has been marked as a duplicate of this bug. ***
Created attachment 43225 [details] New crash information added by DrKonqi Second start of Kontact after booting. The first instance was closed because akonadi did not run correctly. Kontact does not segfault when starting for a third time.
Created attachment 43226 [details] New crash information added by DrKonqi Second start of Kontact after booting. The first instance was closed because akonadi did not run correctly. Kontact does not segfault when starting for a third time.
Created attachment 43227 [details] New crash information added by DrKonqi Second start of Kontact after booting. The first instance was closed because akonadi did not run correctly. Kontact does not segfault when starting for a third time.
Hm, drkonqui failed once with a timeout, I told it to retry once and now there are three comments and attachments. Oops.
> This bug only has 140 votes. The top 5 most hated bugs > all have more than a thousand. > > If you want this bug to get some love, voting for it might help. > Actually, the head Plasma dev already said that he does not take the amount of votes into consideration when deciding what to fix. Furthermore, looking at the 5 most hated bugs, they pretty much get as ignored as every other bug. This is when they were filed: 2002-04-23 2008-01-14 2004-03-17 2003-12-10 2007-05-07 That's an average age of over five years!
Created attachment 43796 [details] New crash information added by DrKonqi As with what seems to be the case on all of the other crashes on the report, this was the second time that kontact had been restarted. The problem I have is that I do use akonadi, and the resource agent doesn't start up on the first initialisation. I'm getting stuck between either my addressbook not working on the first run or kmail crashing on the second run.
I haven't had this Kontact crash since I switched to KDE 4.4.2 on Karmic, but Ryan Gordon is still affected with KDE 4.4.2 on Lucid, and Jon Skanes is affected with KDE 4.4.1 on Karmic. Some possible reasons for my good fortune: - I'm using KDE 4.4.2 from the Launchpad PPA, http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu karmic main - I switched hardware and changed from the i386 Ubuntu variant to amd64. - I copied my data files into a new home directory, so most of my old preferences were destroyed.
*** Bug 237591 has been marked as a duplicate of this bug. ***
*** Bug 240797 has been marked as a duplicate of this bug. ***
*** Bug 240634 has been marked as a duplicate of this bug. ***
*** Bug 239909 has been marked as a duplicate of this bug. ***
*** Bug 238493 has been marked as a duplicate of this bug. ***
*** Bug 234397 has been marked as a duplicate of this bug. ***
*** Bug 231229 has been marked as a duplicate of this bug. ***
*** Bug 234207 has been marked as a duplicate of this bug. ***
*** Bug 241027 has been marked as a duplicate of this bug. ***
Created attachment 48065 [details] New crash information added by DrKonqi kontact shows the bug tracking window on startup. the difference of this backtrace is contact isn't quitting with segmention fault but with aborted. But it seems to be the same bug. Opening kontacts let it crash while starting. now main window is comming up.
*** Bug 242120 has been marked as a duplicate of this bug. ***
Created attachment 48236 [details] New crash information added by DrKonqi Akonadi server does not start before Kontact on boot.. After booting I must "Quit" Kontact, restart Akonadi server.. then start Kontact to get syncing with google to work.. unfortunately the calandar sync seems to have issues I haven't decyphered yet.
Created attachment 48531 [details] proposed patch Can someone who can reproduce the crash (I cannot) please test the attached patch?
Created attachment 49633 [details] New crash information added by DrKonqi I have closed Kontact (ctrl + q) and then reopened it, and then it has crashed. I think that some of the kioslaves associated with Kontact probably were causing this issue.
Created attachment 49637 [details] New crash information added by DrKonqi I just was starting Kontact when it crashed. I think that is related to kioslaves associated with IMAP accounts.
*** Bug 246918 has been marked as a duplicate of this bug. ***
*** Bug 246171 has been marked as a duplicate of this bug. ***
*** Bug 247138 has been marked as a duplicate of this bug. ***
*** Bug 247559 has been marked as a duplicate of this bug. ***
Created attachment 50551 [details] New crash information added by DrKonqi Kontact crashed on start up... This did not happen in a very long time - usually it works.
*** Bug 247367 has been marked as a duplicate of this bug. ***
*** Bug 244054 has been marked as a duplicate of this bug. ***
*** Bug 244825 has been marked as a duplicate of this bug. ***
*** Bug 248089 has been marked as a duplicate of this bug. ***
*** Bug 248694 has been marked as a duplicate of this bug. ***
Created attachment 50849 [details] New crash information added by DrKonqi kontact (4.4.5) on KDE Platform 4.5.00 (KDE 4.5.0) using Qt 4.7.0 Crashed on Kontact restarting. Doesn't matter if Kontact crashed before or was closed manualy. -- Backtrace (Reduced): #7 QString (this=0x6b0000) at /usr/include/qt4/QtCore/qstring.h:727 #8 KontactInterface::Plugin::identifier (this=0x6b0000) at ../../kontactinterface/plugin.cpp:101 #9 0xb7809c3e in Kontact::MainWindow::activateInitialPluginModule (this=0x9f8cea8) at ../../../kontact/src/mainwindow.cpp:289 #10 0xb7809cf4 in Kontact::MainWindow::setInitialActivePluginModule (this=0x9f8cea8, module=...) at ../../../kontact/src/mainwindow.cpp:266 #11 0x0804bd2f in KontactApp::newInstance (this=0xbfc15c34) at ../../../kontact/src/main.cpp:149
*** Bug 249272 has been marked as a duplicate of this bug. ***
*** Bug 250384 has been marked as a duplicate of this bug. ***
*** Bug 249645 has been marked as a duplicate of this bug. ***
*** Bug 249532 has been marked as a duplicate of this bug. ***
*** Bug 246531 has been marked as a duplicate of this bug. ***
*** Bug 255142 has been marked as a duplicate of this bug. ***
*** Bug 256085 has been marked as a duplicate of this bug. ***
*** Bug 256827 has been marked as a duplicate of this bug. ***
[Comment from a bug triager] From bug 256719: - What I was doing when the application crashed: Mail was working yesterday morning. before update. Sent email(reply to one I received) it did not go out for some reason. Tried moving it to another folder, wouldn't move. copied to another folder (Drafts) then tried to delete from outbox and kontact crashed. KDE 4.5.3 (updated yesterday), Kontact 4.4.7, Kmail 1.13.5 Updated backtrace: [KCrash Handler] #6 Kontact::MainWindow::activateInitialPluginModule (this=0x7aa760) at /usr/src/debug/kdepim-4.4.7/kontact/src/mainwindow.cpp:289 #7 0x00000000004034ea in KontactApp::newInstance (this=0x7fffae415780) at /usr/src/debug/kdepim-4.4.7/kontact/src/main.cpp:149 #8 0x00007f055007e318 in KUniqueApplicationAdaptor::newInstance (this=0x782180, asn_id=<value optimized out>, args=...) at /usr/src/debug/kdelibs-4.5.3/kdeui/kernel/kuniqueapplication.cpp:440 #9 0x00007f055007e392 in KUniqueApplicationAdaptor::qt_metacall (this=0x782180, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffae414970)
*** Bug 254967 has been marked as a duplicate of this bug. ***
*** Bug 256719 has been marked as a duplicate of this bug. ***
From bug 257815: - What I was doing when the application crashed: I've just restarted Kontact and it crashed. I think that it was caused since it has tried to open IMAP folders. - Custom settings of the application: I have about 4 IMAP accounts, for different domains. Two of them at Google Mail.
*** Bug 257815 has been marked as a duplicate of this bug. ***
Created attachment 53960 [details] New crash information added by DrKonqi kontact (4.6 pre) on KDE Platform 4.5.80 (4.6 Beta1) using Qt 4.7.1 - What I was doing when the application crashed: Yesterday I installed (or better said, a system update installed) KMail2. The mails were imported but I have a folder with lots of mails from kde lists. As akonadi takes too many ressources to index this folder, I tried to delete it. That is not possible directly inside KMail as the "Move to trash" does nothing. So I went to the filesystem and manually deleted the folder and the corresponding .ids files. When I restarted KMail, I got this crash. -- Backtrace (Reduced): #7 deref (this=0x816b92c, other=...) at ../../src/corelib/arch/qatomic_i386.h:132 #8 QString::operator= (this=0x816b92c, other=...) at tools/qstring.cpp:1358 #9 0xb7836dfd in Kontact::MainWindow::setInitialActivePluginModule (this=0x816b8c8, module=...) at /usr/src/debug/kdepim-4.5.80/kontact/src/mainwindow.cpp:265 #10 0x0804a968 in KontactApp::newInstance (this=0xbfe9a594) at /usr/src/debug/kdepim-4.5.80/kontact/src/main.cpp:147 #11 0xb75bfbb7 in KUniqueApplicationAdaptor::newInstance (this=0x80f3fd0, asn_id=..., args=...) at /usr/src/debug/kdelibs-4.5.80/kdeui/kernel/kuniqueapplication.cpp:436
[Comment from a bug triager] From bug 258697: -- Information about the crash: Starte Kontact manually. Seemd to be stuck on checking IMAP accounts. Progress bar stayed at less than 20%. Hit stop bar and progress bar jumped to 81%. However the status did not change. Closed Kontact and received crash message. Had not been doing anything else. The crash can be reproduced every time.
*** Bug 258697 has been marked as a duplicate of this bug. ***
4.6 Beta 2 still has this. I can confirm what Christian said in comment #9: it happens on every second start. So you can rather easily trigger this: start Kontact, open Akregator inside, quit Kontact, start Kontact again. Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb2d1f710 (LWP 7029))] Thread 3 (Thread 0xb05dab70 (LWP 7030)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb4015125 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb60fc24c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6 #3 0xb59d7987 in ?? () from /usr/lib/libQtWebKit.so.4 #4 0xb4010b25 in start_thread () from /lib/libpthread.so.0 #5 0xb60ee46e in clone () from /lib/libc.so.6 Thread 2 (Thread 0xa9de5b70 (LWP 7353)): #0 0xb3f7b22b in clock_gettime () from /lib/librt.so.1 #1 0xb6df9265 in do_gettime () at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb6eccd26 in updateCurrentTime (this=0xe2c08c4, tm=...) at kernel/qeventdispatcher_unix.cpp:339 #4 QTimerInfoList::timerWait (this=0xe2c08c4, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0xb6ecb55b in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xa9de511c) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb6ecb5fd in timerSourcePrepare (source=0xe2c0890, timeout=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:169 #7 0xb3ece0c0 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #8 0xb3ecef22 in ?? () from /usr/lib/libglib-2.0.so.0 #9 0xb3ecf60e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #10 0xb6ecbda7 in QEventDispatcherGlib::processEvents (this=0xe2c2458, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0xb6e9c89d in QEventLoop::processEvents (this=0xa9de52b0, flags=...) at kernel/qeventloop.cpp:149 #12 0xb6e9cac9 in QEventLoop::exec (this=0xa9de52b0, flags=...) at kernel/qeventloop.cpp:201 #13 0xb6d9b7a9 in QThread::exec (this=0xd6f6650) at thread/qthread.cpp:490 #14 0xb6e7c4ad in QInotifyFileSystemWatcherEngine::run (this=0xd6f6650) at io/qfilesystemwatcher_inotify.cpp:248 #15 0xb6d9e39a in QThreadPrivate::start (arg=0xd6f6650) at thread/qthread_unix.cpp:285 #16 0xb4010b25 in start_thread () from /lib/libpthread.so.0 #17 0xb60ee46e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb2d1f710 (LWP 7029)): [KCrash Handler] #7 0xb76e06eb in QString (this=0x826b408) at /usr/include/QtCore/qstring.h:728 #8 KontactInterface::Plugin::identifier (this=0x826b408) at /usr/src/debug/kdepimlibs-4.5.86svn1205247/kontactinterface/plugin.cpp:101 #9 0xb770ed43 in Kontact::MainWindow::activateInitialPluginModule (this=0x8167238) at /usr/src/debug/kdepim-4.5.86svn1205247/kontact/src/mainwindow.cpp:289 #10 0xb770edf5 in Kontact::MainWindow::setInitialActivePluginModule (this=0x8167238, module=...) at /usr/src/debug/kdepim-4.5.86svn1205247/kontact/src/mainwindow.cpp:266 #11 0x0804a968 in KontactApp::newInstance (this=0xbf97bbf4) at /usr/src/debug/kdepim-4.5.86svn1205247/kontact/src/main.cpp:147 #12 0xb74a0347 in KUniqueApplicationAdaptor::newInstance (this=0x80e7530, asn_id=..., args=...) at /usr/src/debug/kdelibs-4.5.86svn1205247/kdeui/kernel/kuniqueapplication.cpp:436 #13 0xb74a041c in KUniqueApplicationAdaptor::qt_metacall (this=0x80e7530, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf97b1ac) at /usr/src/debug/kdelibs-4.5.86svn1205247/build/kdeui/kuniqueapplication_p.moc:81 #14 0xb479fe17 in QDBusConnectionPrivate::deliverCall (this=0x806d218, object=0x80e7530, msg=..., metaTypes=..., slotIdx=-1080578264) at qdbusintegrator.cpp:919 #15 0xb47a0d58 in QDBusConnectionPrivate::activateCall (this=0x806d218, object=0x80e7530, flags=337, msg=...) at qdbusintegrator.cpp:829 #16 0xb47a1428 in QDBusConnectionPrivate::activateObject (this=0x806d218, node=..., msg=..., pathStartPos=135734064) at qdbusintegrator.cpp:1399 #17 0xb47a1928 in QDBusActivateObjectEvent::placeMetaCall (this=0xd3feda8) at qdbusintegrator.cpp:1493 #18 0xb6eb2b7f in QObject::event (this=0xbf97bbf4, e=0xd3feda8) at kernel/qobject.cpp:1211 #19 0xb6e9dbaa in QCoreApplication::event (this=0xbf97bbf4, e=0xd3feda8) at kernel/qcoreapplication.cpp:1561 #20 0xb63b7c2d in QApplication::event (this=0xbf97bbf4, e=0xd3feda8) at kernel/qapplication.cpp:2486 #21 0xb63b5414 in QApplicationPrivate::notify_helper (this=0x8077138, receiver=0xbf97bbf4, e=0xd3feda8) at kernel/qapplication.cpp:4445 #22 0xb63be137 in QApplication::notify (this=0xbf97bbf4, receiver=0xbf97bbf4, e=0xd3feda8) at kernel/qapplication.cpp:3845 #23 0xb74995b1 in KApplication::notify (this=0xbf97bbf4, receiver=0xbf97bbf4, event=0xd3feda8) at /usr/src/debug/kdelibs-4.5.86svn1205247/kdeui/kernel/kapplication.cpp:311 #24 0xb6e9d5be in QCoreApplication::notifyInternal (this=0xbf97bbf4, receiver=0xbf97bbf4, event=0xd3feda8) at kernel/qcoreapplication.cpp:732 #25 0xb6ea134c in sendEvent (receiver=0x0, event_type=0, data=0x8056c28) at kernel/qcoreapplication.h:215 #26 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8056c28) at kernel/qcoreapplication.cpp:1373 #27 0xb6ea149c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266 #28 0xb6ecbbd4 in sendPostedEvents (s=0x807ef38) at kernel/qcoreapplication.h:220 #29 postEventSourceDispatch (s=0x807ef38) at kernel/qeventdispatcher_glib.cpp:277 #30 0xb3eceb49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #31 0xb3ecf350 in ?? () from /usr/lib/libglib-2.0.so.0 #32 0xb3ecf60e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #33 0xb6ecbd5b in QEventDispatcherGlib::processEvents (this=0x8075948, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #34 0xb646b9aa in QGuiEventDispatcherGlib::processEvents (this=0x8075948, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #35 0xb6e9c89d in QEventLoop::processEvents (this=0xbf97bb54, flags=...) at kernel/qeventloop.cpp:149 #36 0xb6e9cac9 in QEventLoop::exec (this=0xbf97bb54, flags=...) at kernel/qeventloop.cpp:201 #37 0xb6ea1570 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #38 0xb63b3114 in QApplication::exec () at kernel/qapplication.cpp:3719 #39 0x0804b707 in main (argc=) at /usr/src/debug/kdepim-4.5.86svn1205247/kontact/src/main.cpp:217
I've not suffered this problem with KDE 4.5.4 (kdepim 4.4.8) Can't say about 4.6 as that crashes for other reasons. Sorry for not reporting earlier that it has fixed for me for some time.
Created attachment 55037 [details] New crash information added by DrKonqi kontact (4.4.7) on KDE Platform 4.5.3 (KDE 4.5.3) "release 10" using Qt 4.6.3 - What I was doing when the application crashed: After awaking from standby I shutdown Kontact and restartet it. It crashed immediatly. -- Backtrace (Reduced): #8 0xb7861d23 in Kontact::MainWindow::activateInitialPluginModule() () from /usr/lib/libkontactprivate.so.4 #9 0xb7861dd5 in Kontact::MainWindow::setInitialActivePluginModule(QString const&) () from /usr/lib/libkontactprivate.so.4 #10 0x0804ab20 in KontactApp::newInstance() () #11 0xb7366183 in KUniqueApplicationAdaptor::newInstance(QByteArray const&, QByteArray const&) () from /usr/lib/libkdeui.so.5 #12 0xb736623c in KUniqueApplicationAdaptor::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkdeui.so.5
For me it crashed without having opened akregator explicitely, i.e. I never clicked on the icon in the speedbar on the left. The akregator icon in the systray is enabled though. Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 Kontact::MainWindow::activateInitialPluginModule (this=0x652ca0) at /usr/src/debug/kdepim-4.4.8/kontact/src/mainwindow.cpp:289 #7 0x00000000004034ea in KontactApp::newInstance (this=0x7fffcde308c0) at /usr/src/debug/kdepim-4.4.8/kontact/src/main.cpp:149 #8 0x00007fc4b62757b8 in KUniqueApplicationAdaptor::newInstance (this=0x7dfe40, asn_id=<value optimized out>, args=...) at /usr/src/debug/kdelibs-4.5.4/kdeui/kernel/kuniqueapplication.cpp:440 #9 0x00007fc4b6275832 in KUniqueApplicationAdaptor::qt_metacall (this=0x7dfe40, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffcde2fab0) at /usr/src/debug/kdelibs-4.5.4/build/kdeui/kuniqueapplication_p.moc:81 #10 0x00007fc4b2d2f188 in QDBusConnectionPrivate::deliverCall (this=0x62fa10, object=0x7dfe40, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:904 #11 0x00007fc4b2d31245 in QDBusConnectionPrivate::activateCall (this=0x62fa10, object=0x7dfe40, flags=337, msg=...) at qdbusintegrator.cpp:816 #12 0x00007fc4b2d31aae in QDBusConnectionPrivate::activateObject (this=0x62fa10, node=..., msg=..., pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1364 #13 0x00007fc4b2d31cf8 in QDBusActivateObjectEvent::placeMetaCall (this=0x1c1b8a0) at qdbusintegrator.cpp:1477 #14 0x00007fc4b586e509 in QObject::event (this=0x7fffcde308c0, e=0x1c1b8a0) at kernel/qobject.cpp:1248 #15 0x00007fc4b4c50b0d in QApplication::event (this=0x7fffcde308c0, e=0x1c1b8a0) at kernel/qapplication.cpp:2355 #16 0x00007fc4b4c4e4d4 in QApplicationPrivate::notify_helper (this=0x63f9d0, receiver=0x7fffcde308c0, e=0x1c1b8a0) at kernel/qapplication.cpp:4302 #17 0x00007fc4b4c56aca in QApplication::notify (this=<value optimized out>, receiver=0x7fffcde308c0, e=0x1c1b8a0) at kernel/qapplication.cpp:4185 #18 0x00007fc4b6182816 in KApplication::notify (this=0x7fffcde308c0, receiver=0x7fffcde308c0, event=0x1c1b8a0) at /usr/src/debug/kdelibs-4.5.4/kdeui/kernel/kapplication.cpp:310 #19 0x00007fc4b585ce4c in QCoreApplication::notifyInternal (this=0x7fffcde308c0, receiver=0x7fffcde308c0, event=0x1c1b8a0) at kernel/qcoreapplication.cpp:726 #20 0x00007fc4b58605ba in sendEvent (receiver=0x0, event_type=0, data=0x60db90) at kernel/qcoreapplication.h:215 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x60db90) at kernel/qcoreapplication.cpp:1367 #22 0x00007fc4b5885173 in sendPostedEvents (s=<value optimized out>) at kernel/qcoreapplication.h:220 #23 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276 #24 0x00007fc4acea8a93 in g_main_dispatch (context=0x64a520) at gmain.c:1960 #25 IA__g_main_context_dispatch (context=0x64a520) at gmain.c:2513 #26 0x00007fc4acea9270 in g_main_context_iterate (context=0x64a520, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2591 #27 0x00007fc4acea9510 in IA__g_main_context_iteration (context=0x64a520, may_block=1) at gmain.c:2654 #28 0x00007fc4b588567f in QEventDispatcherGlib::processEvents (this=0x613220, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412 #29 0x00007fc4b4cef14e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #30 0x00007fc4b585c292 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #31 0x00007fc4b585c495 in QEventLoop::exec (this=0x7fffcde30810, flags=...) at kernel/qeventloop.cpp:201 #32 0x00007fc4b586088b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #33 0x000000000040417e in main (argc=1, argv=0x7fffcde30ea8) at /usr/src/debug/kdepim-4.4.8/kontact/src/main.cpp:224
(In reply to comment #143) > Created an attachment (id=55037) [details] > New crash information added by DrKonqi > > kontact (4.4.7) on KDE Platform 4.5.3 (KDE 4.5.3) "release 10" using Qt 4.6.3 > > - What I was doing when the application crashed: > > After awaking from standby I shutdown Kontact and restartet it. It crashed > immediatly. > > -- Backtrace (Reduced): > #8 0xb7861d23 in Kontact::MainWindow::activateInitialPluginModule() () from > /usr/lib/libkontactprivate.so.4 > #9 0xb7861dd5 in Kontact::MainWindow::setInitialActivePluginModule(QString > const&) () from /usr/lib/libkontactprivate.so.4 > #10 0x0804ab20 in KontactApp::newInstance() () > #11 0xb7366183 in KUniqueApplicationAdaptor::newInstance(QByteArray const&, > QByteArray const&) () from /usr/lib/libkdeui.so.5 > #12 0xb736623c in KUniqueApplicationAdaptor::qt_metacall(QMetaObject::Call, > int, void**) () from /usr/lib/libkdeui.so.5 I didn't start Akgregator either. Like described in my Comment #143 I suspend my system to disk, awake it and close Kontact. When I restart it it crashes immediately and when I restart it a second time everything works fine. This is always reproducible.
I am a newbie, but have been sending crash reports on this issue for sometime. I won't pretend to understand the backtraces and I will accept that within those, there is an indication that the problem is related in someway to Plasma or Qt4. However is there any chance that any of these bugs is tied to Akonadi? I ask because it seems that my ability to sync with my Google calendar and contacts as well as eGroupware on a local server fails as well. I notice that some of these bug reports (I realize that I may be commenting on the wrong bug here) are related to IMAP issues, which if I understand correctly Kontact handles outside of Akonadi. What I seem to see happening most of the time for me is related to doing something related to Akonadi though. Like adding a new calendar or trying to figure out why Google calendar is no longer in sync. Given all the moving parts and having been out of the coding world for 20+ years I am only offering "out of the box" comments. All of this may have been reviewed already. Sometimes it takes someone asking stupid questions though. On Wednesday 22 December 2010 5:50:37 am ranc0ur@web.de wrote: > https://bugs.kde.org/show_bug.cgi?id=193514 > > > > > > --- Comment #145 from <ranc0ur web de> 2010-12-22 12:50:13 --- > (In reply to comment #143) > > > Created an attachment (id=55037) > > --> (http://bugs.kde.org/attachment.cgi?id=55037) [details] > > > New crash information added by DrKonqi > > > > kontact (4.4.7) on KDE Platform 4.5.3 (KDE 4.5.3) "release 10" using Qt > > 4.6.3 > > > > - What I was doing when the application crashed: > > > > After awaking from standby I shutdown Kontact and restartet it. It > > crashed immediatly. > > > > -- Backtrace (Reduced): > > #8 0xb7861d23 in Kontact::MainWindow::activateInitialPluginModule() () > > from /usr/lib/libkontactprivate.so.4 > > #9 0xb7861dd5 in > > Kontact::MainWindow::setInitialActivePluginModule(QString const&) () > > from /usr/lib/libkontactprivate.so.4 > > #10 0x0804ab20 in KontactApp::newInstance() () > > #11 0xb7366183 in KUniqueApplicationAdaptor::newInstance(QByteArray > > const&, QByteArray const&) () from /usr/lib/libkdeui.so.5 > > #12 0xb736623c in > > KUniqueApplicationAdaptor::qt_metacall(QMetaObject::Call, int, void**) > > () from /usr/lib/libkdeui.so.5 > > I didn't start Akgregator either. Like described in my Comment #143 I > suspend my system to disk, awake it and close Kontact. When I restart it > it crashes immediately and when I restart it a second time everything > works fine. This is always reproducible.
*** Bug 262209 has been marked as a duplicate of this bug. ***
Created attachment 56588 [details] New crash information added by DrKonqi kontact (4.4.9) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.0 same crash as in bug #226815, but with kmail 1.13.5, Kontact 4.4.9, and KDE 4.6.0. same symptoms as in that bug except that the progress bar was stuck at 0% instead of 80%. -- Backtrace (Reduced): #6 Kontact::MainWindow::activateInitialPluginModule (this=0x1636130) at ../../../kontact/src/mainwindow.cpp:289 #7 0x00000000004043f2 in KontactApp::newInstance (this=0x7fff18f1df60) at ../../../kontact/src/main.cpp:149 #8 0x00007fc21b4562b2 in KUniqueApplicationAdaptor::newInstance (this=0x16e5b50, asn_id=<value optimized out>, args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:436 #9 0x00007fc21b456916 in KUniqueApplicationAdaptor::qt_metacall (this=0x16e5b50, _c=QMetaObject::InvokeMetaMethod, _id=28569296, _a=0x7fff18f1d100) at ./kuniqueapplication_p.moc:81 #10 0x00007fc217d730ee in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>) at qdbusintegrator.cpp:919
*** Bug 266101 has been marked as a duplicate of this bug. ***
*** Bug 266098 has been marked as a duplicate of this bug. ***
this crash happened to me again after i did these steps: 1. open a large IMAP folder (>10000 messages). 2. select all messages. 3. press Delete. 4. wait a while for KMail to start deleting messages. 5. realizing that the messages were being downloaded and moved to the local Trash folder instead of being deleted, cancel the delete job via the progress panel. 6. observing that KMail continues to download the messages that were going to be deleted, close KMail. 7. open KMail.
Created attachment 57438 [details] New crash information added by DrKonqi kontact (4.4.8) on KDE Platform 4.5.3 (KDE 4.5.3) using Qt 4.7.0 - What I was doing when the application crashed: After suspending the PC to RAM and then waking up again I turned of the Kontact because of known bug with lost connection to IMAP. After a hour or two I tried to start Kontact again, but it crashed. After pressing the button "Restart the application" Kontact started normally. -- Backtrace (Reduced): #6 Kontact::MainWindow::activateInitialPluginModule (this=0x1b63720) at ../../../kontact/src/mainwindow.cpp:289 #7 0x0000000000404722 in KontactApp::newInstance (this=0x7fff9b1b57e0) at ../../../kontact/src/main.cpp:149 #8 0x00007fa95f705146 in KUniqueApplicationAdaptor::newInstance (this=0x1b5d5f0, asn_id=<value optimized out>, args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:440 #9 0x00007fa95f705786 in KUniqueApplicationAdaptor::qt_metacall (this=0x1b5d5f0, _c=QMetaObject::InvokeMetaMethod, _id=31462192, _a=0x7fff9b1b4980) at ./kuniqueapplication_p.moc:81 #10 0x00007fa95c0b195e in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>) at qdbusintegrator.cpp:919
(In reply to comment #152) > Created an attachment (id=57438) [details] > New crash information added by DrKonqi > > kontact (4.4.8) on KDE Platform 4.5.3 (KDE 4.5.3) using Qt 4.7.0 > > - What I was doing when the application crashed: > > After suspending the PC to RAM and then waking up again I turned of the Kontact > because of known bug with lost connection to IMAP. After a hour or two I tried > to start Kontact again, but it crashed. After pressing the button "Restart the > application" Kontact started normally. > > -- Backtrace (Reduced): > #6 Kontact::MainWindow::activateInitialPluginModule (this=0x1b63720) at > ../../../kontact/src/mainwindow.cpp:289 > #7 0x0000000000404722 in KontactApp::newInstance (this=0x7fff9b1b57e0) at > ../../../kontact/src/main.cpp:149 > #8 0x00007fa95f705146 in KUniqueApplicationAdaptor::newInstance > (this=0x1b5d5f0, asn_id=<value optimized out>, args=...) at > ../../kdeui/kernel/kuniqueapplication.cpp:440 > #9 0x00007fa95f705786 in KUniqueApplicationAdaptor::qt_metacall > (this=0x1b5d5f0, _c=QMetaObject::InvokeMetaMethod, _id=31462192, > _a=0x7fff9b1b4980) at ./kuniqueapplication_p.moc:81 > #10 0x00007fa95c0b195e in QDBusConnectionPrivate::deliverCall (this=<value > optimized out>, object=<value optimized out>, msg=<value optimized out>, > metaTypes=..., slotIdx=<value optimized out>) > at qdbusintegrator.cpp:919 Well this is EXACTLY what happens to me, I don't have the abilities to solve this problem or give any hint but I'd like to help out. So if someone knows how to deal with it I'd love to give feedback. This Bug is open for over a year, so it's about time to do something... ;)
*** Bug 266986 has been marked as a duplicate of this bug. ***
*** Bug 267199 has been marked as a duplicate of this bug. ***
*** Bug 267841 has been marked as a duplicate of this bug. ***
*** Bug 267804 has been marked as a duplicate of this bug. ***
Created attachment 57899 [details] New crash information added by DrKonqi kontact (4.4.9) on KDE Platform 4.6.1 (4.6.1) using Qt 4.7.0 - What I was doing when the application crashed: I stopped kontact, and a few minutes later i started it. -- Backtrace (Reduced): #7 0x0083884c in QString (this=0x886e930) at /usr/include/qt4/QtCore/qstring.h:727 #8 KontactInterface::Plugin::identifier (this=0x886e930) at ../../kontactinterface/plugin.cpp:101 #9 0x0045c75e in Kontact::MainWindow::activateInitialPluginModule (this=0x8502c90) at ../../../kontact/src/mainwindow.cpp:289 #10 0x0045c814 in Kontact::MainWindow::setInitialActivePluginModule (this=0x8502c90, module=...) at ../../../kontact/src/mainwindow.cpp:266 #11 0x0804b9ef in KontactApp::newInstance (this=0xbfb97e94) at ../../../kontact/src/main.cpp:149
Created attachment 57972 [details] New crash information added by DrKonqi kontact (4.4.9) on KDE Platform 4.6.1 (4.6.1) using Qt 4.7.0 suspended (s3) computer, then wake from suspend. Kontact gives an error about being unable to connect to the imap server. Close kontact and try to reopen kontact, it can't be opened again (kontact will not open unless I open with 'kontact --module kmail'; the software finally opens with the --module flag and then kontact crashes.) -- Backtrace (Reduced): #6 Kontact::MainWindow::activateInitialPluginModule (this=0xc77ca0) at ../../../kontact/src/mainwindow.cpp:289 #7 0x00000000004043f2 in KontactApp::newInstance (this=0x7fff67d95040) at ../../../kontact/src/main.cpp:149 #8 0x00007fa51a7c2b42 in KUniqueApplicationAdaptor::newInstance (this=0xcf0bf0, asn_id=<value optimized out>, args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:436 #9 0x00007fa51a7c31a6 in KUniqueApplicationAdaptor::qt_metacall (this=0xcf0bf0, _c=QMetaObject::InvokeMetaMethod, _id=18105840, _a=0x7fff67d941e0) at ./kuniqueapplication_p.moc:81 #10 0x00007fa5170d80ee in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>) at qdbusintegrator.cpp:919
(In reply to comment #159) > suspended (s3) computer, then wake from suspend. Kontact gives an error about > being unable to connect to the imap server. > > Close kontact and try to reopen kontact, it can't be opened again (kontact will > not open unless I open with 'kontact --module kmail'; the software finally > opens with the --module flag and then kontact crashes.) Check your processes. I guess kontact is still running which would be another bug, i.e. kontact does not close after it messes-up its imap connection due to a suspend.
*** Bug 268804 has been marked as a duplicate of this bug. ***
*** Bug 269358 has been marked as a duplicate of this bug. ***
*** Bug 270157 has been marked as a duplicate of this bug. ***
*** Bug 269842 has been marked as a duplicate of this bug. ***
*** Bug 271985 has been marked as a duplicate of this bug. ***
Created attachment 59509 [details] New crash information added by DrKonqi kontact (4.6 beta4) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2 The this pointer of the first to lines is 0xb, so there is likely a stale or NULL pointer involved here. -- Backtrace (Reduced): #7 QString (this=0xb) at /usr/include/QtCore/qstring.h:728 #8 KontactInterface::Plugin::identifier (this=0xb) at /usr/src/debug/kdepimlibs-4.6.2/kontactinterface/plugin.cpp:101 #9 0xb76dad43 in Kontact::MainWindow::activateInitialPluginModule (this=0x816a5f0) at /usr/src/debug/kdepim-4.6.40.git.1301325577/kontact/src/mainwindow.cpp:289 #10 0xb76dadf5 in Kontact::MainWindow::setInitialActivePluginModule (this=0x816a5f0, module=...) at /usr/src/debug/kdepim-4.6.40.git.1301325577/kontact/src/mainwindow.cpp:266 #11 0x0804a9d8 in KontactApp::newInstance (this=0xbff0c7b4) at /usr/src/debug/kdepim-4.6.40.git.1301325577/kontact/src/main.cpp:147
Created attachment 59516 [details] New crash information added by DrKonqi kontact (4.4.11) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2 This is the first time it crashed for me during startup. Usually this crash happened while using the application. -- Backtrace (Reduced): #7 0xb76eb12c in QString (this=0x8ade100) at /usr/include/qt4/QtCore/qstring.h:728 #8 KontactInterface::Plugin::identifier (this=0x8ade100) at /var/tmp/portage/kde-base/kdepimlibs-4.6.2-r1/work/kdepimlibs-4.6.2/kontactinterface/plugin.cpp:101 #9 0xb787c37f in Kontact::MainWindow::activateInitialPluginModule (this=0x8ae93a0) at /var/tmp/portage/kde-base/kontact-4.4.11.1/work/kontact-4.4.11.1/kontact/src/mainwindow.cpp:289 #10 0xb787c425 in Kontact::MainWindow::setInitialActivePluginModule (this=0x8ae93a0, module=...) at /var/tmp/portage/kde-base/kontact-4.4.11.1/work/kontact-4.4.11.1/kontact/src/mainwindow.cpp:266 #11 0x0804be05 in KontactApp::newInstance (this=0xbfe513e4) at /var/tmp/portage/kde-base/kontact-4.4.11.1/work/kontact-4.4.11.1/kontact/src/main.cpp:149
Created attachment 60273 [details] New crash information added by DrKonqi kontact (4.4.11) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.3 - What I was doing when the application crashed: Kontact crashes at startup. If try to open it again works fine. -- Backtrace (Reduced): #6 Kontact::MainWindow::activateInitialPluginModule (this=0x2461490) at /home/anke/desktop-testing/kdepim/src/kdepim-4.4.11.1/kontact/src/mainwindow.cpp:289 #7 0x00000000004034ca in KontactApp::newInstance (this=0x7fffbf5b4d60) at /home/anke/desktop-testing/kdepim/src/kdepim-4.4.11.1/kontact/src/main.cpp:149 #8 0x00007fc9517901a2 in KUniqueApplicationAdaptor::newInstance (this=0x24050c0, asn_id=<value optimized out>, args=...) at /home/manutortosa/desktop-testing/kdelibs/src/kdelibs-4.6.3/kdeui/kernel/kuniqueapplication.cpp:436 #9 0x00007fc951790242 in KUniqueApplicationAdaptor::qt_metacall (this=0x24050c0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffbf5b3e10) at /home/manutortosa/desktop-testing/kdelibs/src/build/kdeui/kuniqueapplication_p.moc:81 [...] #14 0x00007fc9500c9cca in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
*** Bug 275599 has been marked as a duplicate of this bug. ***
I am seeing this in Kubuntu Natty Kontact Version 4.4.10 KDE - Be Free! Platform Version 4.6.2 (4.6.2) Not using Akregator but it is installed and I am using Akonadi
Forgot to mention I am using IMAP not POP
Created attachment 61733 [details] New crash information added by DrKonqi kontact (4.4.11) on KDE Platform 4.6.4 (4.6.4) using Qt 4.7.3 Re-Starting KMail, having used an IMAP account previously. -- Backtrace (Reduced): #6 activateInitialPluginModule (this=0x888ab0) at ../../../kontact/src/mainwindow.cpp:289 #7 Kontact::MainWindow::activateInitialPluginModule (this=0x888ab0) at ../../../kontact/src/mainwindow.cpp:284 #8 0x0000000000404472 in KontactApp::newInstance (this=0x7fff34176e60) at ../../../kontact/src/main.cpp:149 #9 0x00000031b465bd82 in KUniqueApplicationAdaptor::newInstance (this=0x818710, asn_id=<value optimized out>, args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:436 #10 0x00000031b465be22 in KUniqueApplicationAdaptor::qt_metacall (this=0x818710, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff34175fd0) at ./kuniqueapplication_p.moc:81
I'm still puzzled about this report, none of the methods to trigger this crash work here. There's probably another condition. So, if someone is able to reproduce this crash *every time* (with your regular user and with a new one, for example), please report how to do. So far, I tried the following things: - suspend to ram then wake up - use kontact (which is the opposite of the previous point) - "Relaunching Kontact after I had closed it once. I haven't logged out and in again." - start Kontact, open Akregator inside, quit Kontact, start Kontact again. - "When I closed Kontact I had the Journal module opened" - "Closing Kontact (ctrl+q) and reopening results in a crash." Bonus point if you use kdepim >= 4.6
I am still on KDE 4.6.2 and Kontact 4.4.10 (as before) but I am not now getting a crash every time. If I logged out or restarted then, last time I tried to use Kontact regularly, I found a pop up warning of another kontact running. If I pressed exit and then started Kontact, it crashed. Now it does not crash (or has not the several times I have tried today whereas, previously, it crashed every time. I have got rid of the popup, another kontact is running, by excluding Kontact from the KDE restore session and explicitly starting it at login (automatically not manually). I will give this a go for a few days and see if it remains fixed
*** Bug 278729 has been marked as a duplicate of this bug. ***
(In reply to comment #174) > [...] I found a pop up warning of another kontact running. If I > pressed exit and then started Kontact, it crashed. this was a different issue that is fixed with kdepim >= 4.6.0
*** Bug 279137 has been marked as a duplicate of this bug. ***
*** Bug 280768 has been marked as a duplicate of this bug. ***
My crash problems happen when Akregator refreshes an RSS feed when the filter in the feed subject pane is set at unread. At a refresh, certain RSS feeds bleed more listings than are tallied for the feed. selecting one of the new listings I believe causes an error condition since the count in the left pane versus the feeds shown are incorrect. If you select another feed in the left pane, then go back to the last selection, the counts correct themselves, and the detail pane now shows the correct number that are currently unread. When this error condition happens, it does not immediately crash Kontact, it is when Kontact is closed then reopened when the warning popup for the seg fault happens. I would suggest looking at the code that controls the metadata history when a filter (Unread, New) is used on the detail pane. When a malformed RSS listing arrives, it must get by the handling code and produces the fault.
Dear All, I've recently updated to KDE 4.7 using the new Kmail 4.7.0 and I don't see this problem anymore. Shoudn't this bug be marked as "Fixed in version" ? My system info: KDE Development Platform: 4.7.00 (4.7.0) Qt: 4.7.2 Kontact: 4.7.0 KMail: 4.7.0
Appears to be the same for me: KDE 4.7.00 (4.7.0) QT 4.7.2 Kontact 4.7.0 KMail 4.7.0
*** Bug 281644 has been marked as a duplicate of this bug. ***
*** Bug 284289 has been marked as a duplicate of this bug. ***
*** Bug 286861 has been marked as a duplicate of this bug. ***
A possible fix was pushed a few days ago. If you can reliably reproduce this crash, please retry when kdepim 4.7.4 or 4.8beta1 are out
Hi there, I hope we'll have an appropriate fix in F16 soon thanx! Piotr On Thu, 17 Nov 2011 17:12:16 Christophe Giboudeaux wrote: > https://bugs.kde.org/show_bug.cgi?id=193514 > > > > > > --- Comment #185 from Christophe Giboudeaux <cgiboudeaux gmx com> > 2011-11-17 17:12:14 --- A possible fix was pushed a few days ago. If you > can reliably reproduce this crash, please retry when kdepim 4.7.4 or > 4.8beta1 are out
*** Bug 287446 has been marked as a duplicate of this bug. ***
Created attachment 66060 [details] New crash information added by DrKonqi kontact (4.7.2) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 - What I was doing when the application crashed: Opening a mail which caused the problem...this was a mail with a possibility to react: "Accept", "Tentative", "Decline". I have manually removed the mail via webmail. -- Backtrace (Reduced): #7 0xb7689afb in QString (other=..., this=0xbfa8ddc8) at /usr/include/qt4/QtCore/qstring.h:728 #8 KontactInterface::Plugin::identifier (this=0x8e5c330) at ../../kontactinterface/plugin.cpp:101 #9 0xb76b803f in activateInitialPluginModule (this=0x8c4e7c0) at ../../../kontact/src/mainwindow.cpp:318 #10 Kontact::MainWindow::activateInitialPluginModule (this=0x8c4e7c0) at ../../../kontact/src/mainwindow.cpp:313 #11 0xb76b80f5 in Kontact::MainWindow::setInitialActivePluginModule (this=0x8c4e7c0, module=...) at ../../../kontact/src/mainwindow.cpp:295
*** Bug 287584 has been marked as a duplicate of this bug. ***
I fixed this last night. should be fixed in KDE 4.8.0
*** Bug 289403 has been marked as a duplicate of this bug. ***
Clearing the CC list
*** Bug 290415 has been marked as a duplicate of this bug. ***
Created attachment 67622 [details] New crash information added by DrKonqi kontact (4.8 rc2) on KDE Platform 4.7.97 (4.8 RC2 (4.7.97) "release 1" using Qt 4.8.0 - What I was doing when the application crashed: Crash on startup -- feels pretty much as the same crash as in previous Kontact versions (and Dr Konqui's dupe finder tells me it is the same crash). -- Backtrace (Reduced): #6 0xb781b7ab in QString (other=..., this=0xbfa1d624) at /usr/include/QtCore/qstring.h:725 #7 KontactInterface::Plugin::identifier (this=0x8382370) at /usr/src/debug/kdepimlibs-4.7.97/kontactinterface/plugin.cpp:101 #8 0xb784b5e0 in activateInitialPluginModule (this=0x8191758) at /usr/src/debug/kdepim-4.7.97/kontact/src/mainwindow.cpp:319 #9 Kontact::MainWindow::activateInitialPluginModule (this=0x8191758) at /usr/src/debug/kdepim-4.7.97/kontact/src/mainwindow.cpp:314 #10 0xb784b6d5 in Kontact::MainWindow::setInitialActivePluginModule (this=0x8191758, module=...) at /usr/src/debug/kdepim-4.7.97/kontact/src/mainwindow.cpp:296
*** Bug 291101 has been marked as a duplicate of this bug. ***
*** Bug 291632 has been marked as a duplicate of this bug. ***
Not fixed. Here the backtrace of 4.8.1: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb2689710 (LWP 2381))] Thread 4 (Thread 0xb1479b70 (LWP 2382)): #0 0xb3d04782 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0xb61503ac in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6 #2 0xb5904189 in ?? () from /usr/lib/libQtWebKit.so.4 #3 0xb59041cf in ?? () from /usr/lib/libQtWebKit.so.4 #4 0xb3d00a7d in start_thread () from /lib/libpthread.so.0 #5 0xb614289e in clone () from /lib/libc.so.6 Thread 3 (Thread 0xb0b51b70 (LWP 2383)): #0 0xb3d03a74 in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0 #1 0xb6150604 in pthread_mutex_unlock () from /lib/libc.so.6 #2 0xb3c1943f in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #3 0xb3c1a207 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb3c1a7fa in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb647c5a7 in QEventDispatcherGlib::processEvents (this=0xb0200468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0xb644840d in QEventLoop::processEvents (this=0xb0b512d0, flags=...) at kernel/qeventloop.cpp:149 #7 0xb64486a9 in QEventLoop::exec (this=0xb0b512d0, flags=...) at kernel/qeventloop.cpp:204 #8 0xb6332d0c in QThread::exec (this=0x8163268) at thread/qthread.cpp:501 #9 0xb6332dfb in QThread::run (this=0x8163268) at thread/qthread.cpp:568 #10 0xb63361f0 in QThreadPrivate::start (arg=0x8163268) at thread/qthread_unix.cpp:298 #11 0xb3d00a7d in start_thread () from /lib/libpthread.so.0 #12 0xb614289e in clone () from /lib/libc.so.6 Thread 2 (Thread 0xaea61b70 (LWP 3672)): #0 0xb3d02ae6 in pthread_mutex_lock () from /lib/libpthread.so.0 #1 0xb61505c4 in pthread_mutex_lock () from /lib/libc.so.6 #2 0xb3c18cd7 in g_main_context_release () from /usr/lib/libglib-2.0.so.0 #3 0xb3c1a4d6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb3c1a7fa in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb647c5a7 in QEventDispatcherGlib::processEvents (this=0xae100468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0xb644840d in QEventLoop::processEvents (this=0xaea612a0, flags=...) at kernel/qeventloop.cpp:149 #7 0xb64486a9 in QEventLoop::exec (this=0xaea612a0, flags=...) at kernel/qeventloop.cpp:204 #8 0xb6332d0c in QThread::exec (this=0x9c5b6e8) at thread/qthread.cpp:501 #9 0xb642597d in QInotifyFileSystemWatcherEngine::run (this=0x9c5b6e8) at io/qfilesystemwatcher_inotify.cpp:248 #10 0xb63361f0 in QThreadPrivate::start (arg=0x9c5b6e8) at thread/qthread_unix.cpp:298 #11 0xb3d00a7d in start_thread () from /lib/libpthread.so.0 #12 0xb614289e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb2689710 (LWP 2381)): [KCrash Handler] #6 QString (other=) at /usr/include/QtCore/qstring.h:725 #7 KontactInterface::Plugin::identifier (this=0x7468002f) at /usr/src/debug/kdepimlibs-4.8.1/kontactinterface/plugin.cpp:101 #8 0xb77fa050 in activateInitialPluginModule (this=0x81970e8) at /usr/src/debug/kdepim-4.8.1/kontact/src/mainwindow.cpp:320 #9 Kontact::MainWindow::activateInitialPluginModule (this=0x81970e8) at /usr/src/debug/kdepim-4.8.1/kontact/src/mainwindow.cpp:315 #10 0xb77fa145 in Kontact::MainWindow::setInitialActivePluginModule (this=0x81970e8, module=...) at /usr/src/debug/kdepim-4.8.1/kontact/src/mainwindow.cpp:297 #11 0x0804ba78 in KontactApp::newInstance (this=0xbfa41034) at /usr/src/debug/kdepim-4.8.1/kontact/src/main.cpp:147 #12 0xb756aa07 in KUniqueApplicationAdaptor::newInstance (this=0x81640d0, asn_id=..., args=...) at /usr/src/debug/kdelibs-4.8.1/kdeui/kernel/kuniqueapplication.cpp:442 #13 0xb756aab8 in qt_static_metacall (_a=0xbfa4060c, _id=0, _o=0x81640d0, _c=<optimized out>) at /usr/src/debug/kdelibs-4.8.1/build/kdeui/kuniqueapplication_p.moc:58 #14 KUniqueApplicationAdaptor::qt_static_metacall (_o=0x81640d0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfa4060c) at /usr/src/debug/kdelibs-4.8.1/build/kdeui/kuniqueapplication_p.moc:52 #15 0xb756ac2c in KUniqueApplicationAdaptor::qt_metacall (this=0x81640d0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbfa4060c) at /usr/src/debug/kdelibs-4.8.1/build/kdeui/kuniqueapplication_p.moc:102 #16 0xb449f610 in QDBusConnectionPrivate::deliverCall (this=0x806c248, object=0x81640d0, msg=..., metaTypes=..., slotIdx=-1079770252) at qdbusintegrator.cpp:947 #17 0xb44a08e0 in QDBusConnectionPrivate::activateCall (this=0x806c248, object=0x81640d0, flags=337, msg=...) at qdbusintegrator.cpp:857 #18 0xb44a10ab in QDBusConnectionPrivate::activateObject (this=0x806c248, node=..., msg=..., pathStartPos=-1079769248) at qdbusintegrator.cpp:1443 #19 0xb44a1458 in QDBusActivateObjectEvent::placeMetaCall (this=0x8510808) at qdbusintegrator.cpp:1537 #20 0xb646478b in QObject::event (this=0xbfa41034, e=0x8510808) at kernel/qobject.cpp:1204 #21 0xb6449eaa in QCoreApplication::event (this=0xbfa41034, e=0x8510808) at kernel/qcoreapplication.cpp:1688 #22 0xb69d39bd in QApplication::event (this=0xbfa41034, e=0x8510808) at kernel/qapplication.cpp:2532 #23 0xb69cf2f4 in notify_helper (e=0x8510808, receiver=0xbfa41034, this=0x8075058) at kernel/qapplication.cpp:4550 #24 QApplicationPrivate::notify_helper (this=0x8075058, receiver=0xbfa41034, e=0x8510808) at kernel/qapplication.cpp:4522 #25 0xb69d4703 in QApplication::notify (this=0x8510808, receiver=0xbfa41034, e=0x8510808) at kernel/qapplication.cpp:4279 #26 0xb7564881 in KApplication::notify (this=0xbfa41034, receiver=0xbfa41034, event=0x8510808) at /usr/src/debug/kdelibs-4.8.1/kdeui/kernel/kapplication.cpp:311 #27 0xb644989e in QCoreApplication::notifyInternal (this=0xbfa41034, receiver=0xbfa41034, event=0x8510808) at kernel/qcoreapplication.cpp:876 #28 0xb644d518 in sendEvent (event=<optimized out>, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #29 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8053258) at kernel/qcoreapplication.cpp:1500 #30 0xb644d84c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1393 #31 0xb647c154 in sendPostedEvents () at kernel/qcoreapplication.h:236 #32 postEventSourceDispatch (s=0x8074ee8) at kernel/qeventdispatcher_glib.cpp:279 #33 0xb3c19e2f in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #34 0xb3c1a560 in ?? () from /usr/lib/libglib-2.0.so.0 #35 0xb3c1a7fa in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #36 0xb647c547 in QEventDispatcherGlib::processEvents (this=0x8052e88, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #37 0xb6a8310a in QGuiEventDispatcherGlib::processEvents (this=0x8052e88, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #38 0xb644840d in QEventLoop::processEvents (this=0xbfa40f94, flags=...) at kernel/qeventloop.cpp:149 #39 0xb64486a9 in QEventLoop::exec (this=0xbfa40f94, flags=...) at kernel/qeventloop.cpp:204 #40 0xb644d8fa in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #41 0xb69cd164 in QApplication::exec () at kernel/qapplication.cpp:3811 #42 0x0804af91 in main (argc=) at /usr/src/debug/kdepim-4.8.1/kontact/src/main.cpp:218
which(pim) applications are installed on your machine and which are enabled in kontact ?
(In reply to comment #198) > which(pim) applications are installed on your machine and which are enabled > in kontact ? KMail, KOrganizer (rarely used), and Akregaror which seems to cause this -- as it has done before. That particular crash happened after I subscribed to a RSS feed by clicking on it in Firefox which first launched Akregator stand alone. Then after quitting Akregator, I launched Kontact to get this bug. Another bug report tied this crash to a fault in Metakit. It was closed as dupe of this bug.
*** Bug 296199 has been marked as a duplicate of this bug. ***
*** Bug 297233 has been marked as a duplicate of this bug. ***
Created attachment 70413 [details] New crash information added by DrKonqi kontact (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1 - What I was doing when the application crashed: kontact crashed at second start after quitting cleanly the first time. This is the trace for KDE 4.8.2. I used all the following modules : kmail, kaddressbook and akregator nefore closing -- Backtrace (Reduced): #6 activateInitialPluginModule (this=0xc4b510) at ../../../kontact/src/mainwindow.cpp:320 #7 Kontact::MainWindow::activateInitialPluginModule (this=0xc4b510) at ../../../kontact/src/mainwindow.cpp:315 #8 0x000000000040410a in KontactApp::newInstance (this=0x7fffd90c8410) at ../../../kontact/src/main.cpp:147 #9 0x00007f2e8db52522 in KUniqueApplicationAdaptor::newInstance (this=0xc21d20, asn_id=<optimized out>, args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:442 #10 0x00007f2e8db525c2 in KUniqueApplicationAdaptor::qt_metacall (this=0xc21d20, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffd90c76a0) at ./kuniqueapplication_p.moc:81
Created attachment 70914 [details] New crash information added by DrKonqi kontact (4.8.3) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1 - What I was doing when the application crashed: > and Akregaror which seems to cause this -- as it has done before. That particular crash happened after I subscribed to a RSS feed Same for me on 4.8.3. -- Backtrace (Reduced): #6 QString (other=<error reading variable: Cannot access memory at address 0xffc29a90ffcda2ab>, this=0x7fff8423a390) at /usr/include/qt4/QtCore/qstring.h:725 #7 KontactInterface::Plugin::identifier (this=0xffc29a90ffcda29b) at ../../kontactinterface/plugin.cpp:101 #8 0x00007f976ca2357f in activateInitialPluginModule (this=0x1ae9c80) at ../../../kontact/src/mainwindow.cpp:320 #9 Kontact::MainWindow::activateInitialPluginModule (this=0x1ae9c80) at ../../../kontact/src/mainwindow.cpp:315 #10 0x000000000040410a in KontactApp::newInstance (this=0x7fff8423b550) at ../../../kontact/src/main.cpp:147
Can confirm that this bug is back in 4.8.2 kontact: symbol lookup error: /usr/lib64/libkaddressbookprivate.so.4: undefined symbol: _ZN7Akonadi28StandardContactActionManager32setCollectionPropertiesPageNamesERK11QStringList
Thomas Arend it's not back for you. Just fix your distro. You don't use good kdepimlibs and kdepim. => for you it's invalid
*** Bug 307341 has been marked as a duplicate of this bug. ***
*** Bug 315104 has been marked as a duplicate of this bug. ***
#6 0xb779202c in Kontact::Plugin::identifier (this=0x900806e) at /usr/include/qt4/QtCore/qstring.h:711 #7 0xb77abff9 in Kontact::MainWindow::activatePluginModule (this=0x9028dc8) at /build/buildd/kdepim-4.2.90/kontact/src/mainwindow.cpp:300 #8 0xb77ac0a4 in Kontact::MainWindow::setActivePluginModule (this=0x9028dc8, module=@0xbf81bbd4) at /build/buildd/kdepim-4.2.90/kontact/src/mainwindow.cpp:278 #9 0x0804ac57 in KontactApp::newInstance (this=0xbf81c738) at /build/buildd/kdepim-4.2.90/kontact/src/main.cpp:147 #10 0xb6c4b516 in KUniqueApplicationAdaptor::newInstance (this=0x90888e8, asn_id=@0xa631d18, args=@0x9f49f88) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kuniqueapplication.cpp:454 #11 0xb6c4b5be in KUniqueApplicationAdaptor::qt_metacall (this=0x90888e8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf81be28) at /build/buildd/kde4libs-4.2.90/obj-i486-linux-gnu/kdeui/kuniqueapplication_p.moc:75 #12 0xb5c79e2a in QDBusConnectionPrivate::deliverCall (this=0x9010e68, object=0x90888e8, msg=@0xaef7558, metaTypes=@0xa014d94, slotIdx=4) at qdbusintegrator.cpp:891 #13 0xb5c7b149 in QDBusConnectionPrivate::activateCall (this=0x9010e68, object=0x90888e8, flags=337, msg=@0xaef7558) at qdbusintegrator.cpp:803 #14 0xb5c7b5b1 in QDBusConnectionPrivate::activateObject (this=0x9010e68, node=@0xaef7544, msg=@0xaef7558, pathStartPos=16) at qdbusintegrator.cpp:1375 #15 0xb5c7baaa in QDBusActivateObjectEvent::placeMetaCall (this=0xaef7518) at qdbusintegrator.cpp:1469 #16 0xb5b72150 in QObject::event (this=0xbf81c738, e=0xaef7518) at kernel/qobject.cpp:1118 <a href="http://www.immobilier-tamansourt.com"> Kech </a>
Git commit ea9ef72d49d4d79e22f5b1fe9d5d9fb44eeea207 by Allen Winter. Committed on 06/09/2015 at 15:21. Pushed by winterz into branch 'KDE/4.14'. main.cpp - wrap mMainWindow in QPointer for safety 5 year old patch from Christopher Feck to solve the activatePlugin crash MERGE: safe for merging to modern versions M +1 -1 kontact/src/main.cpp http://commits.kde.org/kdepim/ea9ef72d49d4d79e22f5b1fe9d5d9fb44eeea207
Git commit 5e0ae7519e8440f3d8920588ba51fad365ff50f3 by Montel Laurent. Committed on 07/09/2015 at 07:05. Pushed by mlaurent into branch 'Applications/15.08'. Backport: main.cpp - wrap mMainWindow in QPointer for safety 5 year old patch from Christopher Feck to solve the activatePlugin crash M +1 -1 kontact/src/main.cpp http://commits.kde.org/kdepim/5e0ae7519e8440f3d8920588ba51fad365ff50f3