Application: kmail (2.0.89) KDE Platform Version: 4.6.2 (4.6.2) Qt Version: 4.7.2 Operating System: Linux 2.6.38-CHAKRA x86_64 -- Information about the crash: - What I was doing when the application crashed: Opened Kmail instant crash. - Custom settings of the application:Added a Gmail IMAP account and set it to check on start. If I delete all kmail 2 settings and nepomuk entries in my home folder Kmail resets and I'm able to open it without crashing. As soon as I set up the IMAP account kmail crashes. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted [Current thread is 1 (Thread 0x7fc49d765760 (LWP 6117))] Thread 2 (Thread 0x7fc47f8c1710 (LWP 6122)): #0 0x00007fc49890040c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x00007fc48f569de4 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/libQtWebKit.so.4 #2 0x00007fc48f569e19 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/libQtWebKit.so.4 #3 0x00007fc4988fbcb0 in start_thread () from /lib/libpthread.so.0 #4 0x00007fc49aa759fd in clone () from /lib/libc.so.6 #5 0x0000000000000000 in ?? () Thread 1 (Thread 0x7fc49d765760 (LWP 6117)): [KCrash Handler] #6 0x00007fc49a9d9595 in raise () from /lib/libc.so.6 #7 0x00007fc49a9daa16 in abort () from /lib/libc.so.6 #8 0x00007fc49b290a6f in qt_message_output(QtMsgType, char const*) () from /usr/lib/libQtCore.so.4 #9 0x00007fc49b290bfd in qt_message(QtMsgType, char const*, __va_list_tag*) () from /usr/lib/libQtCore.so.4 #10 0x00007fc49b290d95 in qFatal(char const*, ...) () from /usr/lib/libQtCore.so.4 #11 0x00007fc498b717b2 in QDBusPendingReplyData::argumentAt(int) const () from /usr/lib/libQtDBus.so.4 #12 0x00007fc494ffc128 in KSieveUi::Util::findSieveUrlForAccount(QString const&) () from /usr/lib/libksieveui.so.4 #13 0x00007fc495000cea in KSieveUi::Vacation::findURL() const () from /usr/lib/libksieveui.so.4 #14 0x00007fc495000e2b in KSieveUi::Vacation::Vacation(QObject*, bool, char const*) () from /usr/lib/libksieveui.so.4 #15 0x00007fc49c5175f7 in KMMainWidget::slotCheckVacation() () from /usr/lib/libkmailprivate.so.4 #16 0x00007fc49c5307ad in KMMainWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4 #17 0x00007fc49b3a933a in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #18 0x00007fc49b8e667c in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #19 0x00007fc49b88d9a4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #20 0x00007fc49b892d11 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #21 0x00007fc49d17e856 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #22 0x00007fc49b392ddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #23 0x00007fc49b396d62 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #24 0x00007fc49b3c0ee3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib/libQtCore.so.4 #25 0x00007fc49327fc33 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #26 0x00007fc493280410 in ?? () from /usr/lib/libglib-2.0.so.0 #27 0x00007fc4932806ad in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #28 0x00007fc49b3c107f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #29 0x00007fc49b93e98e in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtGui.so.4 #30 0x00007fc49b391892 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #31 0x00007fc49b391adc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #32 0x00007fc49b39705b in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #33 0x00000000004030fe in _start () This bug may be a duplicate of or related to bug 266096. Possible duplicates by query: bug 266096. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 266096 ***