Sometimes the akonadi maildir resource crashes. As far as I have observed it, it only happens when I change to mail in another folder. However it does not always happen and so far I was not able to find exact steps to reproduce it. However it happens quite regularly for me. This is using the th 19.03.80 version of KDE applications. Backtrace is attached Linux/KDE Plasma: 5.15.4 KDE Frameworks Version: 5.56 Qt Version: 5.12.2 Akonadi 19.03.80 ADDITIONAL INFORMATION Application: akonadi_maildir_resource (akonadi_maildir_resource), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb12be1f900 (LWP 17409))] Thread 4 (Thread 0x7fb1132f0700 (LWP 17462)): [KCrash Handler] #6 0x00007fb12880c0e0 in raise () from /lib64/libc.so.6 #7 0x00007fb12880d6c1 in abort () from /lib64/libc.so.6 #8 0x00007fb128e3be83 in ?? () from /usr/lib64/libstdc++.so.6 #9 0x00007fb128e41dd8 in ?? () from /usr/lib64/libstdc++.so.6 #10 0x00007fb128e41e23 in std::terminate() () from /usr/lib64/libstdc++.so.6 #11 0x00007fb1291c193b in qTerminate () at global/qglobal.cpp:3192 #12 0x00007fb1291e596b in QThreadPrivate::start (arg=0x55e74a3d8c80) at thread/qthread_unix.cpp:373 #13 0x00007fb12620d569 in start_thread () from /lib64/libpthread.so.0 #14 0x00007fb1288ce81f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fb113af1700 (LWP 17459)): #0 0x00007fb1288c407b in poll () from /lib64/libc.so.6 #1 0x00007fb1243ca129 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fb1243ca23c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fb12941b87b in QEventDispatcherGlib::processEvents (this=0x55e74a3bc6a0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x00007fb1293bcaaa in QEventLoop::exec (this=this@entry=0x7fb113af0c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x00007fb1291e403a in QThread::exec (this=<optimized out>) at thread/qthread.cpp:531 #6 0x00007fb12a103d55 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x00007fb1291e57e2 in QThreadPrivate::start (arg=0x7fb12a37bd80) at thread/qthread_unix.cpp:361 #8 0x00007fb12620d569 in start_thread () from /lib64/libpthread.so.0 #9 0x00007fb1288ce81f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fb118b94700 (LWP 17434)): #0 0x00007fb1288c407b in poll () from /lib64/libc.so.6 #1 0x00007fb11f512387 in ?? () from /usr/lib64/libxcb.so.1 #2 0x00007fb11f513fba in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x00007fb11b9897d8 in QXcbEventQueue::run (this=0x55e74a348300) at qxcbeventqueue.cpp:228 #4 0x00007fb1291e57e2 in QThreadPrivate::start (arg=0x55e74a348300) at thread/qthread_unix.cpp:361 #5 0x00007fb12620d569 in start_thread () from /lib64/libpthread.so.0 #6 0x00007fb1288ce81f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fb12be1f900 (LWP 17409)): #0 0x00007fb126214c34 in pthread_getspecific () from /lib64/libpthread.so.0 #1 0x00007fb1243f1dd0 in g_thread_self () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fb1243ca22d in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fb12941b87b in QEventDispatcherGlib::processEvents (this=0x55e74a327e80, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x00007fb1293bcaaa in QEventLoop::exec (this=this@entry=0x7fffb7ae3e00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x00007fb1293c5cb0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1363 #6 0x00007fb12b366b4d in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib64/libKF5AkonadiAgentBase.so.5 #7 0x000055e748e20271 in ?? () #8 0x00007fb1287f6f4a in __libc_start_main () from /lib64/libc.so.6 #9 0x000055e748e200fa in ?? () [Inferior 1 (process 17409) detached]
This is bug 401692, which was supposed to be fixed for the 19.04.0 release. It is possible that your snapshot didn't yet have commit https://commits.kde.org/akonadi/06f1a32b5a5aa3f5a5dcf842e8de1358480fede5 Would you be able to check this?
Ah wait, 19.03.80 was released March 22, while the commit was made March 25. *** This bug has been marked as a duplicate of bug 401692 ***