Created attachment 109503 [details] Akonadi self test log Pls. refer to attached log
Apparently the same bug for me: Application: akonadi_control (akonadi_control), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb67e747800 (LWP 2636))] Thread 3 (Thread 0x7fb66e7b7700 (LWP 2639)): #0 0x00007ffea83fc9d9 in ?? () #1 0x00007ffea83fcbdc in clock_gettime () #2 0x00007fb67d799876 in clock_gettime () from /lib64/libc.so.6 #3 0x00007fb67dea59e1 in qt_clock_gettime (ts=0x7fb66e7b6ab0, clock=1) at kernel/qelapsedtimer_unix.cpp:175 #4 do_gettime (frac=<synthetic pointer>, sec=<synthetic pointer>) at kernel/qelapsedtimer_unix.cpp:166 #5 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #6 0x00007fb67dea4219 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fb668004cf0) at kernel/qtimerinfo_unix.cpp:91 #7 0x00007fb67dea4815 in QTimerInfoList::timerWait (this=0x7fb668004cf0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #8 0x00007fb67dea5e3e in timerSourcePrepareHelper (timeout=0x7fb66e7b6b94, src=<optimized out>) at kernel/qeventdispatcher_glib.cpp:161 #9 timerSourcePrepare (source=<optimized out>, timeout=0x7fb66e7b6b94) at kernel/qeventdispatcher_glib.cpp:165 #10 0x00007fb67bc9b739 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #11 0x00007fb67bc9c13b in ?? () from /usr/lib64/libglib-2.0.so.0 #12 0x00007fb67bc9c32c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #13 0x00007fb67dea60bb in QEventDispatcherGlib::processEvents (this=0x7fb668000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #14 0x00007fb67de5309b in QEventLoop::exec (this=this@entry=0x7fb66e7b6d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #15 0x00007fb67dca1e96 in QThread::exec (this=<optimized out>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #16 0x00007fb67e79a545 in ?? () from /usr/lib64/libQt5DBus.so.5 #17 0x00007fb67dcaba67 in QThreadPrivate::start (arg=0x7fb67e814d60) at thread/qthread_unix.cpp:367 #18 0x00007fb67d479554 in start_thread () from /lib64/libpthread.so.0 #19 0x00007fb67d78bccf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fb677144700 (LWP 2638)): #0 0x00007fb67d7812c9 in poll () from /lib64/libc.so.6 #1 0x00007fb67b5becc7 in ?? () from /usr/lib64/libxcb.so.1 #2 0x00007fb67b5c08ea in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x00007fb6783216d9 in QXcbEventReader::run (this=0x5586eb30c9c0) at qxcbconnection.h:409 #4 0x00007fb67dcaba67 in QThreadPrivate::start (arg=0x5586eb30c9c0) at thread/qthread_unix.cpp:367 #5 0x00007fb67d479554 in start_thread () from /lib64/libpthread.so.0 #6 0x00007fb67d78bccf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fb67e747800 (LWP 2636)): [KCrash Handler] #6 0x00007fb67d6c908b in raise () from /lib64/libc.so.6 #7 0x00007fb67d6b24e9 in abort () from /lib64/libc.so.6 #8 0x00007fb67dc6a9ad in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1842 #9 QMessageLogger::fatal (this=this@entry=0x7ffea83f7c30, msg=msg@entry=0x5586eae89518 "Cannot remove old log file '%s': %s") at global/qlogging.cpp:880 #10 0x00005586eae58cfd in akInit (appName=...) at /usr/include/qt5/QtCore/qarraydata.h:206 #11 0x00005586eae7ba62 in AkApplicationBase::init (this=this@entry=0x7ffea83f7dd0) at /usr/include/qt5/QtCore/qstring.h:823 #12 0x00005586eae58f68 in AkApplicationImpl<QGuiApplication>::AkApplicationImpl (loggingCategory=..., argv=0x7ffea83f7f38, argc=@0x7ffea83f7d4c: 1, this=0x7ffea83f7dd0) at /usr/include/qt5/QtCore/qscopedpointer.h:52 #13 main (argc=<optimized out>, argv=0x7ffea83f7f38) at /usr/src/debug/akonadi-server-18.08.1-1.1.x86_64/src/akonadicontrol/main.cpp:55 [Inferior 1 (process 2636) detached]
Something weird in your setup. Can you check that all files in ~/.local/share/akonadi are owned by your user and writable?
(In reply to Daniel Vrátil from comment #2) > Something weird in your setup. Can you check that all files in > ~/.local/share/akonadi are owned by your user and writable? As far as I can see, all files are owned by me and RW and even if they weren't, shouldn't there be a PolKit prompt asking me to fix permissions for me instead of crashing? 🤔
Comment #1 is bug 392092.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Nope, haven't seen this issue for months. Thx and merry xmas Am Donnerstag, 1. Dezember 2022, 05:34:32 CET schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=388196 > > Justin Zobel <justin.zobel@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > > --- Comment #5 from Justin Zobel <justin.zobel@gmail.com> --- > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!