Version: 1.3 (using Devel) OS: Linux Installed from: Compiled sources I am using kde 4.2 beta snapshots on opensuse 11.1 rc1. This is using 64-bit software. Kontact had been working fine since installation (a few weeks ago). Today, it started crashing a few seconds after launching. Most of the time (if not all the time), I would also get a notice that kontact could not access one of my imap folders. I am guessing the crashing has to do with the imap problem. I am including a bactrace below. Application: Kontact (kontact), signal SIGSEGV [?1034h[Thread debugging using libthread_db enabled] 0x00007f860a08cce1 in nanosleep () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7f8610f95750 (LWP 6169))] Thread 1 (Thread 0x7f8610f95750 (LWP 6169)): [KCrash Handler] #5 0x00007f860ae26fde in QMetaObject::indexOfSignal(char const*) const () from /usr/lib64/libQtCore.so.4 #6 0x00007f860ae36a80 in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib64/libQtCore.so.4 #7 0x00007f85f9931e41 in KMail::ActionScheduler::fetchTimeOut (this=0x1023f30) at /usr/src/debug/kdepim-4.1.82/kmail/actionscheduler.cpp:838 #8 0x00007f85f993608a in KMail::ActionScheduler::qt_metacall (this=0x1023f30, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff18fd9d80) at /usr/src/debug/kdepim-4.1.82/build/kmail/actionscheduler.moc:127 #9 0x00007f860ae35454 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #10 0x00007f860ae2fda3 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #11 0x00007f860bbbf1bd in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #12 0x00007f860bbc6f8a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #13 0x00007f860c98b40b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #14 0x00007f860ae21091 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #15 0x00007f860ae4d1c0 in ?? () from /usr/lib64/libQtCore.so.4 #16 0x00007f860ae4958d in ?? () from /usr/lib64/libQtCore.so.4 #17 0x00007f8604b540db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #18 0x00007f8604b578ad in ?? () from /usr/lib64/libglib-2.0.so.0 #19 0x00007f8604b57a6b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #20 0x00007f860ae494ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #21 0x00007f860bc4f97f in ?? () from /usr/lib64/libQtGui.so.4 #22 0x00007f860ae1f9a2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #23 0x00007f860ae1fb2d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #24 0x00007f860ae21ffd in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #25 0x00000000004048c5 in main (argc=1, argv=0x7fff18fdaf58) at /usr/src/debug/kdepim-4.1.82/kontact/src/main.cpp:218
The backtrace looks similar to the one in bug 155026. May be related.
Marking as duplicate of bug 155026. If you think this is not a duplicate you can re-open this bug report. Thanks :) *** This bug has been marked as a duplicate of bug 155026 ***