https://bugs.kde.org/show_bug.cgi?id=396299
--- Comment #4 from Christoph Feck <cf...@kde.org> --- Unfortunately lacks debug symbols. But maybe a KDEPIM developer recognizes which functions in messagelist depend on timer events. Pasting relevant information from comment #3: terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_M_construct null not valid Thread 1 "kontact" received signal SIGABRT, Aborted. 0x00007ffff486686b in raise () from /usr/lib/libc.so.6 (gdb) thread apply all bt Thread 1 (Thread 0x7ffff7f5e900 (LWP 5149)): #0 0x00007ffff486686b in raise () from /usr/lib/libc.so.6 #1 0x00007ffff485140e in abort () from /usr/lib/libc.so.6 #2 0x00007ffff4e8d44a in __gnu_cxx::__verbose_terminate_handler () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #3 0x00007ffff4e939d6 in __cxxabiv1::__terminate(void (*)()) () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:47 #4 0x00007ffff4e93a13 in std::terminate () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:57 #5 0x00007ffff4e93c48 in __cxxabiv1::__cxa_throw (obj=obj@entry=0x7fffc8011de0, tinfo=0x7ffff517ffd8 <typeinfo for std::logic_error>, dest=0x7ffff4ea9080 <std::logic_error::~logic_error()>) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:95 #6 0x00007ffff4e8f4d1 in std::__throw_logic_error (__s=0x7ffff4f479c0 "basic_string::_M_construct null not valid") from /usr/lib/libstdc++.so.6 #7 0x00007ffff4f2acd0 in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char const*> ( this=0x7fffffffd3a0, __beg=0x0, __end=<optimized out>) at /build/gcc/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/char_traits.h:350 #8 0x00007ffeb713bd84 in ?? () from /usr/lib/libKF5AkonadiSearchPIM.so.5 #9 0x00007ffebe3cb77a in ?? () from /usr/lib/libKF5MessageList.so.5 #10 0x00007ffebe41a907 in ?? () from /usr/lib/libKF5MessageList.so.5 #11 0x00007ffff5428c50 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #12 0x00007ffff5434c28 in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib/libQt5Core.so.5 #13 0x00007ffff542938b in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #14 0x00007ffff6172a74 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x00007ffff617a341 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x00007ffff53fecb9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #17 0x00007ffff545140a in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #18 0x00007ffff5451c92 in ?? () from /usr/lib/libQt5Core.so.5 #19 0x00007fffee28f368 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #20 0x00007fffee28f5b1 in ?? () from /usr/lib/libglib-2.0.so.0 #21 0x00007fffee28f63e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #22 0x00007ffff5452039 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #23 0x00007fffcf861722 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #24 0x00007ffff53fd94c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #25 0x00007ffff5405c46 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #26 0x00005555555581c9 in ?? () #27 0x00007ffff485306b in __libc_start_main () from /usr/lib/libc.so.6 #28 0x00005555555588fa in _start () -- You are receiving this mail because: You are the assignee for the bug.