SUMMARY Akonadi Birthday Resources closes unexpectedly on boot. it happpens frequently but not at all boots STEPS TO REPRODUCE 1. Boot (May be after a kernel or related package update - not sure) 2. Notification of Akonadi_Borthday_resources crashed unexpectedly. OBSERVED RESULT Akonadi_Borthday_resources crashed unexpectedly EXPECTED RESULT Akonadi_Borthday_resources shouldn't crash at bootup. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 4.19.32-1-lts (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Application: akonadi_birthdays_resource (akonadi_birthdays_resource), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd910bad4c0 (LWP 972))] Thread 4 (Thread 0x7fd8fffff700 (LWP 987)): #0 0x00007fd914e877a4 in read () from /usr/lib/libc.so.6 #1 0x00007fd9134f4961 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x00007fd913544e40 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x00007fd913546636 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x00007fd91354677e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x00007fd9153dacb4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #6 0x00007fd915383a8c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #7 0x00007fd9151c7569 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x00007fd91564eba6 in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x00007fd9151c896c in ?? () from /usr/lib/libQt5Core.so.5 #10 0x00007fd9141e4a9d in start_thread () from /usr/lib/libpthread.so.0 #11 0x00007fd914e96b23 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fd907fff700 (LWP 986)): [KCrash Handler] #6 0x00007fd914dd2d7f in raise () from /usr/lib/libc.so.6 #7 0x00007fd914dbd672 in abort () from /usr/lib/libc.so.6 #8 0x00007fd91500458e in __gnu_cxx::__verbose_terminate_handler () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #9 0x00007fd91500adfa in __cxxabiv1::__terminate (handler=<optimized out>) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:47 #10 0x00007fd91500ae57 in std::terminate () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:57 #11 0x00007fd91518dbd1 in qTerminate() () from /usr/lib/libQt5Core.so.5 #12 0x00007fd91518f6a7 in ?? () from /usr/lib/libQt5Core.so.5 #13 0x00007fd9141e4a9d in start_thread () from /usr/lib/libpthread.so.0 #14 0x00007fd914e96b23 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fd90fb88700 (LWP 977)): #0 0x00007fd914e8bc21 in poll () from /usr/lib/libc.so.6 #1 0x00007fd91444e630 in ?? () from /usr/lib/libxcb.so.1 #2 0x00007fd9144502db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x00007fd910773989 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x00007fd9151c896c in ?? () from /usr/lib/libQt5Core.so.5 #5 0x00007fd9141e4a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x00007fd914e96b23 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fd910bad4c0 (LWP 972)): #0 0x00007fd914e8bc21 in poll () from /usr/lib/libc.so.6 #1 0x00007fd913546690 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x00007fd91354677e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x00007fd9153dacb4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #4 0x00007fd915383a8c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #5 0x00007fd91538bde6 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #6 0x00007fd916a67f6f in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libKF5AkonadiAgentBase.so.5 #7 0x00005629720a79da in ?? () #8 0x00007fd914dbf223 in __libc_start_main () from /usr/lib/libc.so.6 #9 0x000056297209fb7e in _start () [Inferior 1 (process 972) detached]
As per Daniel Vrátil's (dvratil@kde.org) comment on my other bug related to akonadi crash (https://bugs.kde.org/show_bug.cgi?id=405851), which reads "It's an uncaught exception. Might be fixed by https://phabricator.kde.org/D19983" , I believe this is related to that as well and hope it gets fixed as such.
*** This bug has been marked as a duplicate of bug 401692 ***