Bug 424218

Summary: Akonadi fails to start for KOrganizer in Linux Mint 20
Product: [Frameworks and Libraries] Akonadi Reporter: tnpel2925
Component: akonadiconsoleAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: a.samirh78
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mint (Ubuntu based)   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description tnpel2925 2020-07-14 21:59:50 UTC
SUMMARY
After loading into Linux Mint v20, Mate desktop, there is an error "Akonadi Personal Information Service not Running".

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
I had Korganizer running on a laptop with v19.3, and the Cinnamon desktop. Everything ran fine until I loaded V20 with the Mate desktop. I could not get the holidays for the United States to work in the calendar.
Comment 1 mayo 2020-07-16 12:10:32 UTC
Since upgrading Linux Mint to v20, Korganizer won't load because Akonadi fails to start.

2020-07-12T10:11:31 [INFO ] org.kde.pim.akonadiserver: Starting up the Akonadi Server...
2020-07-12T10:11:36 [CRITICAL] org.kde.pim.akonadis2020-07-12T10:11:36 [INFO ] org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
rocess exited unexpectedly during initial connection!
2020-07-12T10:11:36 [CRITICAL] org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld"
2020-07-12T10:11:36 [CRITICAL] org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/alex/.local/share/akonadi/mysql.conf", "--datadir=/home/alex/.local/share/akonadi/db_data/", "--socket=/run/user/1000/akonadi/mysql.socket", "--pid-file=/run/user/1000/akonadi/mysql.pid")
2020-07-12T10:11:36 [CRITICAL] org.kde.pim.akonadiserver: stdout: ""
2020-07-12T10:11:36 [CRITICAL] org.kde.pim.akonadiserver: stderr: "mysqld: [ERROR] Failed to open required defaults file: /home/alex/.local/share/akonadi/mysql.conf\nmysqld: [ERROR] Fatal error in defaults handling. Program aborted!\n"
2020-07-12T10:11:36 [CRITICAL] org.kde.pim.akonadiserver: exit code: 1
2020-07-12T10:11:36 [CRITICAL] org.kde.pim.akonadiserver: process error: "Unknown error"
2020-07-12T10:11:36 [CRITICAL] org.kde.pim.akonadiserver: Failed to remove runtime connection config file
2020-07-12T10:11:36 [INFO ] org.kde.pim.akonadiserver: Shutting down AkonadiServer...
Comment 2 tnpel2925 2020-07-31 19:31:04 UTC
I found a fix for the problem. There are five Akondi programs in the software manager for LM20 but only two are installed. I installed the last three and the calendar works. Only a work-around, but it works.
Comment 3 mayo 2020-07-31 23:23:15 UTC
Thanks. I had already tried that like five times at the time I posted earlier, without success, and had given up hope and switched to Google Calendar using a backup file. But yes, it seems in the interim an update must have fixed it.
Comment 4 mayo 2020-07-31 23:40:19 UTC
Well it seemed to work briefly, then it decided to hang. After a reboot it is back to Akonadi not working.
Comment 5 Ahmad Samir 2020-08-16 14:32:01 UTC
If you have AppArmor enabled, then this looks like a duplicate of bug 411093. (which has a link to a launchpad bug report with a supposed fix).
Comment 6 Justin Zobel 2022-10-12 03:49:51 UTC
Thank you for reporting this crash 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 crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 7 Bug Janitor Service 2022-10-27 05:04:17 UTC
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!
Comment 8 Bug Janitor Service 2022-11-11 05:20:58 UTC
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!