Description of problem: On KDE5 startup the following crash is reported (by KDE's crash reporter). It is not caught by ABRT. Version-Release number of selected component (if applicable): akonadi.x86_64 1.13.0-102.fc24 @@commandline akonadi-import-wizard.x86_64 16.12.3-1.fc25 @updates kdepimlibs-akonadi.x86_64 4.14.10-17.fc25 @updates kf5-akonadi-calendar.x86_64 16.12.3-1.fc25 @updates kf5-akonadi-contacts.x86_64 16.12.3-1.fc25 @updates kf5-akonadi-mime.x86_64 16.12.3-1.fc25 @updates kf5-akonadi-notes.x86_64 16.12.3-1.fc25 @updates kf5-akonadi-search.x86_64 16.12.3-1.fc25 @updates kf5-akonadi-server.x86_64 16.12.3-1.fc25 @updates kf5-akonadi-server-mysql.x86_64 16.12.3-1.fc25 @updates Steps to Reproduce: 1. Reboot. 2. Login to KDE. 3. Window with crash report appears. Expected results: No crash. Additional info: Application: akonadi_control (akonadi_control), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f25d0c6b8c0 (LWP 1892))] Thread 2 (Thread 0x7f25bc6a0700 (LWP 1963)): #0 0x00007f25ced8b01d in poll () at /lib64/libc.so.6 #1 0x00007f25c9a87d10 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x00007f25c9a89aa9 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x00007f25c0d2cd69 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x00007f25cf9a39ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x00007f25cea786ca in start_thread () at /lib64/libpthread.so.0 #6 0x00007f25ced96f7f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f25d0c6b8c0 (LWP 1892)): [KCrash Handler] #6 0x00007f25cecc491f in raise () at /lib64/libc.so.6 #7 0x00007f25cecc651a in abort () at /lib64/libc.so.6 #8 0x00007f25cf98ebb1 in () at /lib64/libQt5Core.so.5 #9 0x000055a369062671 in akInit(QString const&) (appName=...) at /usr/src/debug/akonadi-16.12.3/src/shared/akdebug.cpp:205 #10 0x000055a369060412 in AkApplicationBase::init() (this=0x7ffe6eaee980) at /usr/src/debug/akonadi-16.12.3/src/shared/akapplication.cpp:62 #11 0x000055a36903cbeb in AkApplicationImpl<QGuiApplication>::AkApplicationImpl(int&, char**, QLoggingCategory const&) (loggingCategory=..., argv=0x7ffe6eaeeae8, argc=@0x7ffe6eaee7ec: 1, this=0x7ffe6eaee980) at /usr/src/debug/akonadi-16.12.3/src/shared/akapplication.h:83 #12 0x000055a36903cbeb in main(int, char**) (argc=<optimized out>, argv=0x7ffe6eaeeae8) at /usr/src/debug/akonadi-16.12.3/src/akonadicontrol/main.cpp:56
Still happens with F26: kf5-akonadi-server.x86_64 17.04.1-3.fc26 @@commandline kf5-akonadi-server-debuginfo.x86_64 17.04.1-3.fc26 @fedora-debuginfo kf5-akonadi-server-mysql.x86_64 17.04.1-3.fc26 @@commandline ===================================== Application: akonadi_control (akonadi_control), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9aa1f3bd40 (LWP 1805))] Thread 2 (Thread 0x7f9a8d8db700 (LWP 1817)): #0 0x00007f9aa0042a9d in poll () at /lib64/libc.so.6 #1 0x00007f9a9ad14c97 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x00007f9a9ad16a8a in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x00007f9a91f8cba9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x00007f9aa0c66c9e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x00007f9a9fd2636d in start_thread () at /lib64/libpthread.so.0 #6 0x00007f9aa004eb8f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f9aa1f3bd40 (LWP 1805)): [KCrash Handler] #6 0x00007f9a9ff7466b in raise () at /lib64/libc.so.6 #7 0x00007f9a9ff76470 in abort () at /lib64/libc.so.6 #8 0x00007f9aa0c55527 in () at /lib64/libQt5Core.so.5 #9 0x00005608d8c387fa in akInit(QString const&) (appName=...) at /usr/src/debug/akonadi-17.04.1/src/shared/akdebug.cpp:195 #10 0x00005608d8c36822 in AkApplicationBase::init() (this=0x7ffc82c78a40) at /usr/src/debug/akonadi-17.04.1/src/shared/akapplication.cpp:61 #11 0x00005608d8c16b88 in AkApplicationImpl<QGuiApplication>::AkApplicationImpl(int&, char**, QLoggingCategory const&) (loggingCategory=..., argv=0x7ffc82c78ba8, argc=@0x7ffc82c789bc: 1, this=0x7ffc82c78a40) at /usr/src/debug/akonadi-17.04.1/src/shared/akapplication.h:83 #12 0x00005608d8c16b88 in main(int, char**) (argc=<optimized out>, argv=0x7ffc82c78ba8) at /usr/src/debug/akonadi-17.04.1/src/akonadicontrol/main.cpp:55
Still happens with F27. akonadi.x86_64 1.13.0-107.fc27 @fedora akonadi-import-wizard.x86_64 17.08.1-1.fc27 @fedora kdepimlibs-akonadi.x86_64 4.14.10-22.fc27 @fedora kf5-akonadi-calendar.x86_64 17.08.1-1.fc27 @fedora kf5-akonadi-contacts.x86_64 17.08.1-1.fc27 @fedora kf5-akonadi-mime.x86_64 17.08.1-1.fc27 @fedora kf5-akonadi-notes.x86_64 17.08.1-1.fc27 @fedora kf5-akonadi-search.x86_64 17.08.1-1.fc27 @fedora kf5-akonadi-server.x86_64 17.08.1-3.fc27 @updates-testing kf5-akonadi-server-debuginfo.x86_64 17.08.1-3.fc27 @updates-testing-debuginfo kf5-akonadi-server-debugsource.x86_64 17.08.1-3.fc27 @updates-testing kf5-akonadi-server-mysql.x86_64 17.08.1-3.fc27 @updates-testing kf5-kmailtransport-akonadi.x86_64 17.08.1-1.fc27 @fedora kf5-libkdepim-akonadi.x86_64 17.08.1-1.fc27 @fedora kf5-mailimporter-akonadi.x86_64 17.08.1-1.fc27 @fedora kf5-pimcommon-akonadi.x86_64 17.08.1-1.fc27 @fedora qt5-qtbase.x86_64 5.9.2-1.fc27 @updates-testing qt5-qtbase-common.noarch 5.9.2-1.fc27 @updates-testing qt5-qtbase-debuginfo.x86_64 5.9.2-1.fc27 @updates-testing-debuginfo qt5-qtbase-debugsource.x86_64 5.9.2-1.fc27 @updates-testing qt5-qtbase-devel-debuginfo.x86_64 5.9.2-1.fc27 @updates-testing-debuginfo qt5-qtbase-gui.x86_64 5.9.2-1.fc27 @updates-testing qt5-qtbase-gui-debuginfo.x86_64 5.9.2-1.fc27 @updates-testing-debuginfo qt5-qtbase-mysql.x86_64 5.9.2-1.fc27 @updates-testing ================================================================== Application: akonadi_control (akonadi_control), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f47cf097d40 (LWP 2121))] Thread 2 (Thread 0x7f47bb482700 (LWP 2125)): #0 0x00007f47cc9c0c0b in poll () from /lib64/libc.so.6 #1 0x00007f47c722bfe7 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x00007f47c722ddda in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x00007f47be0219c9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x00007f47cd62b036 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x00007f47cc69b609 in start_thread () from /lib64/libpthread.so.0 #6 0x00007f47cc9cd1bf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f47cf097d40 (LWP 2121)): [KCrash Handler] #6 0x00007f47cc8ea69b in raise () from /lib64/libc.so.6 #7 0x00007f47cc8ec3b1 in abort () from /lib64/libc.so.6 #8 0x00007f47cd619831 in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #9 0x0000561c0cecec2a in akInit (appName=...) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/shared/akdebug.cpp:195 #10 0x0000561c0ceccc42 in AkApplicationBase::init (this=0x7ffee4979f90) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/shared/akapplication.cpp:61 #11 0x0000561c0ceac458 in AkApplicationImpl<QGuiApplication>::AkApplicationImpl (loggingCategory=..., argv=0x7ffee497a0f8, argc=@0x7ffee4979f0c: 1, this=0x7ffee4979f90) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/shared/akapplication.h:83 #12 main (argc=<optimized out>, argv=0x7ffee497a0f8) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/akonadicontrol/main.cpp:55
#8 0x00007f47cd619831 in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 This logged some potential extra information to your user log/journal, can you please try to find this snippet and post that here?
The crash happened again, the data is from this new crash. I found a message which is there just when the crash occurs: Oct 22 09:14:22 omega akonadi_control[2073]: Cannot remove old log file - running on a readonly filesystem maybe? I am going to attach also the full journal/log.
Created attachment 1341750 [details] Output from journalctl -b
The new crash report is similar/the same as the previous one: Application: akonadi_control (akonadi_control), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc9cb46bd40 (LWP 2073))] Thread 2 (Thread 0x7fc9b7856700 (LWP 2075)): #0 0x00007fc9c8d948bb in poll () from /lib64/libc.so.6 #1 0x00007fc9c35fffe7 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x00007fc9c3601dda in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x00007fc9ba3f59c9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x00007fc9c99ff036 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x00007fc9c8a6f609 in start_thread () from /lib64/libpthread.so.0 #6 0x00007fc9c8da0e6f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fc9cb46bd40 (LWP 2073)): [KCrash Handler] #6 0x00007fc9c8cbe69b in raise () from /lib64/libc.so.6 #7 0x00007fc9c8cc03b1 in abort () from /lib64/libc.so.6 #8 0x00007fc9c99ed831 in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #9 0x00005630e443fc2a in akInit (appName=...) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/shared/akdebug.cpp:195 #10 0x00005630e443dc42 in AkApplicationBase::init (this=0x7ffe1c47b850) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/shared/akapplication.cpp:61 #11 0x00005630e441d458 in AkApplicationImpl<QGuiApplication>::AkApplicationImpl (loggingCategory=..., argv=0x7ffe1c47b9b8, argc=@0x7ffe1c47b7cc: 1, this=0x7ffe1c47b850) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/shared/akapplication.h:83 #12 main (argc=<optimized out>, argv=0x7ffe1c47b9b8) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/akonadicontrol/main.cpp:55
I slowly learn how the debuginfo thingy works. Installed more related debuginfo files and got, hopefully, a better report. Executable: akonadi_control PID: 2069 Signal: Aborted (6) Time: 10/22/17 15:20:19 The above mentioned message is still there: Oct 22 15:20:16 omega akonadi_control[2069]: Cannot remove old log file - running on a readonly filesystem maybe? There are no readonly filesystems (that I know of). I will attach the full journal/log. ============================================================ Application: akonadi_control (akonadi_control), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 27 return SYSCALL_CANCEL (nanosleep, requested_time, remaining); [Current thread is 1 (Thread 0x7f57f1680d40 (LWP 2069))] Thread 2 (Thread 0x7f57dda6b700 (LWP 2073)): #0 0x00007f57eefa98bb in __GI___poll (fds=fds@entry=0x7f57dda6ac08, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f57e9814fe7 in poll (__timeout=-1, __nfds=1, __fds=0x7f57dda6ac08) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x562e8675a1c0, cond=cond@entry=0x562e8675a200, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:479 #3 0x00007f57e9816dda in xcb_wait_for_event (c=0x562e8675a1c0) at xcb_in.c:693 #4 0x00007f57e060a9c9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #5 0x00007f57efc14036 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #6 0x00007f57eec84609 in start_thread (arg=0x7f57dda6b700) at pthread_create.c:465 #7 0x00007f57eefb5e6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f57f1680d40 (LWP 2069)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x00007f57eeed53b1 in __GI_abort () at abort.c:79 #8 0x00007f57efc02831 in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #9 0x0000562e8473ac2a in akInit (appName=...) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/shared/akdebug.cpp:195 #10 0x0000562e84738c42 in AkApplicationBase::init (this=0x7ffc8535f6b0) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/shared/akapplication.cpp:61 #11 0x0000562e84718458 in AkApplicationImpl<QGuiApplication>::AkApplicationImpl (loggingCategory=..., argv=0x7ffc8535f818, argc=@0x7ffc8535f62c: 1, this=0x7ffc8535f6b0) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/shared/akapplication.h:83 #12 main (argc=<optimized out>, argv=0x7ffc8535f818) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/akonadicontrol/main.cpp:55
Created attachment 1341787 [details] Output from journalctl -b
The qtbase debuginfo package got updated, it matches the qtbase version now. The crash report seems more complete, it shows the "Cannot remove old log file - running on a readonly filesystem maybe?" message from the journal: Nov 05 09:15:11 omega akonadi_control[2042]: Cannot remove old log file - running on a readonly filesystem maybe? Executable: akonadi_control PID: 2042 Signal: Aborted (6) Time: 11/5/17 09:15:14 Application: akonadi_control (akonadi_control), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 27 return SYSCALL_CANCEL (nanosleep, requested_time, remaining); [Current thread is 1 (Thread 0x7f9b165bcd40 (LWP 2042))] Thread 2 (Thread 0x7f9b02945700 (LWP 2059)): #0 0x00007f9b13eb28bb in __GI___poll (fds=fds@entry=0x7f9b02944bf8, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f9b0e6f3fe7 in poll (__timeout=-1, __nfds=1, __fds=0x7f9b02944bf8) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x5632dc9911f0, cond=cond@entry=0x5632dc991230, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:479 #3 0x00007f9b0e6f5dda in xcb_wait_for_event (c=0x5632dc9911f0) at xcb_in.c:693 #4 0x00007f9b054e4929 in QXcbEventReader::run (this=0x5632dc990740) at qxcbconnection.cpp:1330 #5 0x00007f9b14b20b92 in QThreadPrivate::start (arg=0x5632dc990740) at thread/qthread_unix.cpp:368 #6 0x00007f9b13b8d609 in start_thread (arg=0x7f9b02945700) at pthread_create.c:465 #7 0x00007f9b13ebee6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f9b165bcd40 (LWP 2042)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x00007f9b13dde3b1 in __GI_abort () at abort.c:79 #8 0x00007f9b14b0e637 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1690 #9 QMessageLogger::fatal (this=this@entry=0x7ffe74272450, msg=msg@entry=0x5632db5e6830 "Cannot remove old log file - running on a readonly filesystem maybe?") at global/qlogging.cpp:796 #10 0x00005632db5dcc2a in akInit (appName=...) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/shared/akdebug.cpp:195 #11 0x00005632db5dac42 in AkApplicationBase::init (this=0x7ffe742725f0) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/shared/akapplication.cpp:61 #12 0x00005632db5ba458 in AkApplicationImpl<QGuiApplication>::AkApplicationImpl (loggingCategory=..., argv=0x7ffe74272758, argc=@0x7ffe7427256c: 1, this=0x7ffe742725f0) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/shared/akapplication.h:83 #13 main (argc=<optimized out>, argv=0x7ffe74272758) at /usr/src/debug/kf5-akonadi-server-17.08.1-3.fc27.x86_64/src/akonadicontrol/main.cpp:55
So, apparently akonadi sees that there are existing log files at: ~/.local/share/akonadi/*.old and/or ~/.local/share/akonadi/db_data/*.old and hits an error trying to remove them. Do any of those exist for you? Can you try deleting them?
I am sorry for the late reply. I was travelling abroad. The .old files were there. They were 'fresh' from the last startup. There was no indication showing why Akondi could not remove them (permissions, etc.). $ ll ~/.local/share/akonadi/*.old -rw-rw-r--. 1 tomasz tomasz 148 Nov 29 08:20 /home/tomasz/.local/share/akonadi/akonadi_control.error.old -rw-rw-r--. 1 tomasz tomasz 32 Nov 29 08:20 /home/tomasz/.local/share/akonadi/akonadiserver.error.old $ ll ~/.local/share/akonadi/db_data/*.old -rw-rw-r--. 1 tomasz tomasz 17385157 Nov 29 08:20 /home/tomasz/.local/share/akonadi/db_data/mysql.err.old I logged out and removed them. They were back after KDE startup. I looked into them and found message like 'Cannot connect to / initialize database'. I logged out again and renamed/removed all akonadi files: ll -d ~/.*/*akonadi* ll -d ~/.*/*/*akonadi* ll -d ~/.*/*/*/*akonadi* ll -d ~/.*/*/*/*/*akonadi* It fixed the problem, even KAlarm started to work, first time since ~F24. My problem is solved. Thanks for the help! Unfortunately, the bug in Akonadi stays. The following is my opinion, please take it with a grain of salt. Why the so called 'modern desktop' data have to spread over so many places? What was wrong with the single ~/.akonadi directory approach? We users learned to accept that things go wrong sometimes, and need to be fixed. But, is it not easier to rename/remove a single .akonadi directory, recover it from backups, compare with old ones, than do it on data spread through .config .kde .local/share and since the removal also in .cache?
The issue is back. However there is a slight difference in the logs, it says 'cannot rename' instead of 'cannot remove': Dec 01 06:24:55 omega akonadi_control[2119]: Cannot rename log file - running on a readonly filesystem maybe? $ ll ~/.local/share/akonadi/*.old ~/.local/share/akonadi/db_data/*.old -rw-rw-r--. 1 tomasz tomasz 96 Dec 1 06:31 /home/tomasz/.local/share/akonadi/akonadi_control.error.old -rw-rw-r--. 1 tomasz tomasz 102 Dec 1 06:25 /home/tomasz/.local/share/akonadi/akonadiserver.error.old -rw-rw-r--. 1 tomasz tomasz 16197 Dec 1 06:25 /home/tomasz/.local/share/akonadi/db_data/mysql.err.old Any thoughts? ====================================================== Executable: akonadi_control PID: 2119 Signal: Aborted (6) Time: 12/1/17 06:24:56 Application: akonadi_control (akonadi_control), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 27 return SYSCALL_CANCEL (nanosleep, requested_time, remaining); [Current thread is 1 (Thread 0x7f1896f8ed40 (LWP 2119))] Thread 2 (Thread 0x7f1883317700 (LWP 2122)): #0 0x00007f18948838bb in __GI___poll (fds=fds@entry=0x7f1883316bf8, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f188f0c4fe7 in poll (__timeout=-1, __nfds=1, __fds=0x7f1883316bf8) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x563d6cd7d280, cond=cond@entry=0x563d6cd7d2c0, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:479 #3 0x00007f188f0c6dda in xcb_wait_for_event (c=0x563d6cd7d280) at xcb_in.c:693 #4 0x00007f1885eb5a49 in QXcbEventReader::run (this=0x563d6cd7c7d0) at qxcbconnection.cpp:1335 #5 0x00007f18954f1b92 in QThreadPrivate::start (arg=0x563d6cd7c7d0) at thread/qthread_unix.cpp:368 #6 0x00007f189455e609 in start_thread (arg=0x7f1883317700) at pthread_create.c:465 #7 0x00007f189488fe6f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f1896f8ed40 (LWP 2119)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x00007f18947af3b1 in __GI_abort () at abort.c:79 #8 0x00007f18954df637 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1690 #9 QMessageLogger::fatal (this=this@entry=0x7fff2b4c1690, msg=msg@entry=0x563d6be7f878 "Cannot rename log file - running on a readonly filesystem maybe?") at global/qlogging.cpp:796 #10 0x0000563d6be75c62 in akInit (appName=...) at /usr/src/debug/kf5-akonadi-server-17.08.3-1.fc27.x86_64/src/shared/akdebug.cpp:203 #11 0x0000563d6be73c42 in AkApplicationBase::init (this=0x7fff2b4c1830) at /usr/src/debug/kf5-akonadi-server-17.08.3-1.fc27.x86_64/src/shared/akapplication.cpp:61 #12 0x0000563d6be53458 in AkApplicationImpl<QGuiApplication>::AkApplicationImpl (loggingCategory=..., argv=0x7fff2b4c1998, argc=@0x7fff2b4c17ac: 1, this=0x7fff2b4c1830) at /usr/src/debug/kf5-akonadi-server-17.08.3-1.fc27.x86_64/src/shared/akapplication.h:83 #13 main (argc=<optimized out>, argv=0x7fff2b4c1998) at /usr/src/debug/kf5-akonadi-server-17.08.3-1.fc27.x86_64/src/akonadicontrol/main.cpp:55
Still happens after upgrade to F28. akonadi.x86_64 1.13.0-109.fc28 @fedora akonadi-import-wizard.x86_64 17.12.3-1.fc28 @fedora kdepimlibs-akonadi.x86_64 4.14.10-26.fc28 @fedora kf5-akonadi-calendar.x86_64 17.12.3-1.fc28 @fedora kf5-akonadi-contacts.x86_64 17.12.3-1.fc28 @fedora kf5-akonadi-mime.x86_64 17.12.3-1.fc28 @fedora kf5-akonadi-notes.x86_64 17.12.3-1.fc28 @fedora kf5-akonadi-search.x86_64 17.12.3-1.fc28 @fedora kf5-akonadi-server.x86_64 17.12.3-1.fc28 @fedora kf5-akonadi-server-debuginfo.x86_64 17.12.3-1.fc28 @fedora-debuginfo kf5-akonadi-server-debugsource.x86_64 17.12.3-1.fc28 @fedora-debuginfo kf5-akonadi-server-mysql.x86_64 17.12.3-1.fc28 @fedora kf5-kmailtransport-akonadi.x86_64 17.12.3-1.fc28 @fedora kf5-libkdepim-akonadi.x86_64 17.12.3-1.fc28 @fedora kf5-mailimporter-akonadi.x86_64 17.12.3-1.fc28 @fedora kf5-pimcommon-akonadi.x86_64 17.12.3-1.fc28 @fedora Executable: akonadi_control PID: 1970 Signal: Aborted (6) Time: 4/30/18 15:39:13 Application: akonadi_control (akonadi_control), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 28 return SYSCALL_CANCEL (nanosleep, requested_time, remaining); [Current thread is 1 (Thread 0x7f8c71a80940 (LWP 1970))] Thread 2 (Thread 0x7f8c5e376700 (LWP 1980)): #0 0x00007f8c6f9d3929 in __GI___poll (fds=fds@entry=0x7f8c5e375b78, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f8c6a45304f in poll (__timeout=-1, __nfds=1, __fds=0x7f8c5e375b78) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait () at xcb_conn.c:479 #3 0x00007f8c6a454caa in xcb_wait_for_event (c=0x55a820ce73c0) at xcb_in.c:697 #4 0x00007f8c60d244d9 in QXcbEventReader::run (this=0x55a820ce6ef0) at qxcbconnection.h:409 #5 0x00007f8c706a111d in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #6 0x00007f8c6f6cc564 in start_thread (arg=<optimized out>) at pthread_create.c:463 #7 0x00007f8c6f9de31f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f8c71a80940 (LWP 1970)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x00007f8c6f905591 in __GI_abort () at abort.c:79 #8 0x00007f8c70667ea3 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1716 #9 QMessageLogger::fatal (this=this@entry=0x7fff251ade80, msg=msg@entry=0x55a82033e118 "Cannot rename log file - running on a readonly filesystem maybe?") at global/qlogging.cpp:822 #10 0x000055a820334339 in akInit(QString const&) () at /usr/src/debug/kf5-akonadi-server-17.12.3-1.fc28.x86_64/src/shared/akdebug.cpp:203 #11 0x000055a8203323a6 in AkApplicationBase::init() () at /usr/include/qt5/QtCore/qstring.h:558 #12 0x000055a82030af5c in AkApplicationImpl<QGuiApplication>::AkApplicationImpl (loggingCategory=..., argv=0x7fff251ae188, argc=@0x7fff251adf9c: 1, this=0x7fff251ae020) at /usr/src/debug/kf5-akonadi-server-17.12.3-1.fc28.x86_64/src/akonadicontrol/main.cpp:55 #13 main () at /usr/src/debug/kf5-akonadi-server-17.12.3-1.fc28.x86_64/src/akonadicontrol/main.cpp:55 #14 0x00007f8c6f9071bb in __libc_start_main (main=0x55a82030aec0 <main>, argc=1, argv=0x7fff251ae188, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff251ae178) at ../csu/libc-start.c:308 #15 0x000055a82030b6ca in _start () at /usr/include/qt5/QtCore/qloggingcategory.h:71
#9 QMessageLogger::fatal (this=this@entry=0x7fff251ade80, msg=msg@entry=0x55a82033e118 "Cannot rename log file - running on a readonly filesystem maybe?") at global/qlogging.cpp:822 Same mysql problem as before, mysql is failing, it cannot rename the mysql log file (for some reason).
Fwiw, the akonadi code in question here is fairly straight-forward, I've no idea why your filesystem does not permit deletion/renaming sometimes: const QString name = QFileInfo(appName).fileName(); const auto errorLogFile = DebugPrivate::errorLogFileName(name); QFileInfo infoOld(errorLogFile + QLatin1String(".old")); if (infoOld.exists()) { QFile fileOld(infoOld.absoluteFilePath()); const bool success = fileOld.remove(); if (!success) { qFatal("Cannot remove old log file - running on a readonly filesystem maybe?"); } } QFileInfo info(errorLogFile); if (info.exists()) { QFile file(info.absoluteFilePath()); const bool success = file.copy(errorLogFile + QLatin1String(".old")); if (!success) { qFatal("Cannot rename log file - running on a readonly filesystem maybe?"); } } I found upstream bug #392092 , so seems you're not the only one. :(
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still present in F30: kf5-akonadi-server.x86_64 18.12.2-2.fc30 @fedora Executable: akonadi_control PID: 2109 Signal: Aborted (6) Time: 5/5/19 09:16:42 Application: akonadi_control (akonadi_control), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 29 return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7f6c840b5800 (LWP 2109))] Thread 2 (Thread 0x7f6c76dc5700 (LWP 2113)): #0 0x00007f6c872e72b7 in __GI___poll (fds=0x7f6c76dc4cb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f6c85ed638a in ?? () from /lib64/libxcb.so.1 #2 0x00007f6c85ed7ffa in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x00007f6c76fc7918 in QXcbEventQueue::run (this=0x55dbef0c04a0) at qxcbeventqueue.cpp:228 #4 0x00007f6c8768b8a6 in QThreadPrivate::start (arg=0x55dbef0c04a0) at thread/qthread_unix.cpp:361 #5 0x00007f6c871de5a2 in start_thread (arg=<optimized out>) at pthread_create.c:486 #6 0x00007f6c872f2023 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f6c840b5800 (LWP 2109)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x00007f6c87219895 in __GI_abort () at abort.c:79 #8 0x00007f6c87655af5 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1901 #9 QMessageLogger::fatal (this=this@entry=0x7ffe43400970, msg=msg@entry=0x55dbedbe0a98 "Cannot remove old log file '%s': %s") at global/qlogging.cpp:887 #10 0x000055dbedbae067 in akInit (appName=...) at /usr/include/qt5/QtCore/qarraydata.h:208 #11 0x000055dbedbd2b3b in AkApplicationBase::init (this=this@entry=0x7ffe43400b20) at /usr/include/qt5/QtCore/qstring.h:829 #12 0x000055dbedbae36f in AkApplicationImpl<QGuiApplication>::AkApplicationImpl (loggingCategory=..., argv=0x7ffe43400c88, argc=@0x7ffe43400a9c: 1, this=0x7ffe43400b20) at /usr/include/qt5/QtCore/qscopedpointer.h:52 #13 main (argc=<optimized out>, argv=0x7ffe43400c88) at /usr/src/debug/kf5-akonadi-server-18.12.2-2.fc30.x86_64/src/akonadicontrol/main.cpp:55 [Inferior 1 (process 2109) detached]
#8 0x00007f6c87655af5 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1901\ It added a log entry related to this crash, can you provide fresh logs? Though ideally, this would be best reported upstream at bugs.kde.org , we in fedora have little resources to debug/fix issues of this sort ourselves without upstream collaboration (and particularly if we cannot reproduce the problem ourselves). thanks.
Created attachment 1565281 [details] Output of journalctl -b
I also found the following logs in my home. .local/share/akonadi/akonadi_control.error: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) .local/share/akonadi/akonadi_control.error.old: Unable to register service as "org.freedesktop.Akonadi.Control.lock" Maybe it's already running? .local/share/akonadi/akonadiserver.error: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) .local/share/akonadi/akonadiserver.error.old: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Please let me know, if there are other relevant logs that I can provide.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.