Kontact doesn't start after latest MariaDB update

[cambriz]

This morning I installed an update of the mariadb packages (version 11.4.10) on Mageia 9.

Now I cannot start my email program kontact because the Akonadi service isn´t running.

I tried to manually run

Code: Select all

akonadictl start

but this failed (see attachment).

I don´t know how I can fix this. Can you please help me with this problem?
Access to my email is very important!

[doktor5000]

Can you post the output from

Code: Select all

akonadiselftest
akonadictl status
cat ~/.local/share/akonadi/db_data/mysql.err


and please put them in code-blocks and not in attachments, thanks in advance.

[cambriz]

Code: Select all

(17:34:40) gerald  ~  > $ akonadiselftest
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Database driver found." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The QtSQL driver '%1' is required by your current Akonadi server configuration and was found on your system." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Akonadi is not running as root" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "MySQL server found." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "You have currently configured Akonadi to use the MySQL server '%1'.\nMake sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "MySQL server is executable." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "MySQL server found: %1" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "MySQL server log contains errors." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The MySQL server error log file '%1' contains errors." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "MySQL server default configuration found." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The default configuration for the MySQL server was found and is readable at %1." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "MySQL server custom configuration found." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The custom configuration for the MySQL server was found and is readable at %1" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "MySQL server configuration is usable." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The MySQL server configuration was found at %1 and is readable." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "akonadictl found and usable" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The program '%1' to control the Akonadi server was found and could be executed successfully.\nResult:\n%2" msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Akonadi control process not registered at D-Bus." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Akonadi server process not registered at D-Bus." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Protocol version check not possible." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Without a connection to the server it is not possible to check if the protocol version meets the requirements." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "No resource agents found." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '%1'. The XDG_DATA_DIRS environment variable is set to '%2'; make sure this includes all paths where Akonadi agents are installed." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "No current Akonadi server error log found." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The Akonadi server did not report any errors during its current startup." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "No previous Akonadi server error log found." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The Akonadi server did not report any errors during its previous startup." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "No current Akonadi control error log found." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The Akonadi control process did not report any errors during its current startup." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "No previous Akonadi control error log found." msgid_plural: "" msgctxt: ""
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "The Akonadi control process did not report any errors during its previous startup." msgid_plural: "" msgctxt: ""
(17:34:54) gerald  ~  > $


Code: Select all

(17:34:54) gerald  ~  > $ akonadictl status
Akonadi Control: stopped
Akonadi Server: stopped
Akonadi Server Search Support: available (Remote Search)
Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent, akonadi_birthdays_resource, akonadi_contacts_resource, akonadi_davgroupware_resource, akonadi_ews_resource, akonadi_ewsmta_resource, akonadi_followupreminder_agent, akonadi_google_resource, akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource, akonadi_indexing_agent, akonadi_knut_resource, akonadi_kolab_resource, akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mailfilter_agent, akonadi_mailmerge_agent, akonadi_mbox_resource, akonadi_migration_agent, akonadi_mixedmaildir_resource, akonadi_newmailnotifier_agent, akonadi_notes_agent, akonadi_notes_resource, akonadi_openxchange_resource, akonadi_pop3_resource, akonadi_sendlater_agent, akonadi_tomboynotes_resource, akonadi_unifiedmailbox_agent, akonadi_vcard_resource, akonadi_vcarddir_resource
(17:35:35) gerald  ~  > $


Code: Select all

(17:38:12) gerald  ~  > $ cat ~/.local/share/akonadi/db_data/mysql.err
2026-02-17 17:34:49 0 [Note] Starting MariaDB 11.4.10-MariaDB source revision 054a893f1645b77e52a329a7fc8cf614eebd1fad server_uid +J5I7+Ts2HMJkVxwdq7v+Pyc6m8= as process 13190
2026-02-17 17:34:49 0 [Warning] option 'innodb-log-buffer-size': unsigned value 1048576 adjusted to 2097152
2026-02-17 17:34:49 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2026-02-17 17:34:49 0 [Note] InnoDB: Number of transaction pools: 1
2026-02-17 17:34:49 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2026-02-17 17:34:49 0 [Note] InnoDB: Using Linux native AIO
2026-02-17 17:34:49 0 [Note] InnoDB: innodb_buffer_pool_size_max=128m, innodb_buffer_pool_size=128m
2026-02-17 17:34:49 0 [Note] InnoDB: Completed initialization of buffer pool
2026-02-17 17:34:49 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2026-02-17 17:34:49 0 [Note] InnoDB: End of log at LSN=484800367
2026-02-17 17:34:49 0 [Note] InnoDB: Opened 3 undo tablespaces
2026-02-17 17:34:49 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
2026-02-17 17:34:49 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2026-02-17 17:34:49 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2026-02-17 17:34:49 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2026-02-17 17:34:49 0 [Note] InnoDB: log sequence number 484800367; transaction id 531124
2026-02-17 17:34:49 0 [Note] InnoDB: Loading buffer pool(s) from /home/gerald/.local/share/akonadi/db_data/ib_buffer_pool
2026-02-17 17:34:49 0 [Note] Plugin 'wsrep-provider' is disabled.
2026-02-17 17:34:49 0 [Note] Recovering after a crash using tc.log
2026-02-17 17:34:49 0 [Note] Starting table crash recovery...
2026-02-17 17:34:49 0 [Note] Crash table recovery finished.
2026-02-17 17:34:49 0 [Note] InnoDB: Buffer pool(s) load completed at 260217 17:34:49
2026-02-17 17:34:50 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '11.4.10-MariaDB'  socket: '/run/user/1000/akonadi/mysql.socket'  port: 0  Mageia MariaDB Server
260217 17:34:50 [ERROR] /usr/sbin/mysqld got signal 11 ;
Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs about how to report
a bug on https://jira.mariadb.org/.

Please include the information from the server start above, to the end of the
information below.

Server version: 11.4.10-MariaDB source revision: 054a893f1645b77e52a329a7fc8cf614eebd1fad

The information page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/
contains instructions to obtain a better version of the backtrace below.
Following these instructions will help MariaDB developers provide a fix quicker.

Attempting backtrace. Include this in the bug report.
(note: Retrieving this information may fail)

Thread pointer: 0x7f2b70000c68
stack_bottom = 0x7f2ba8377000 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x3d)[0x10a54bd]
/usr/sbin/mysqld(handle_fatal_signal+0x1ab)[0xae4fcb]
libc_sigaction.c:0(__restore_rt)[0x7f2bb5a649e0]

Connection ID (thread ID): 6
Status: NOT_KILLED
Query (0x7f2b70167d68): SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME, information_schema.KEY_COLUMN_USAGE.COLUMN_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_TABLE_NAME, information_schema.KEY_COLUMN_USAGE.REFERENCED_COLUMN_NAME, information_schema.REFERENTIAL_CONSTRAINTS.UPDATE_RULE, information_schema.REFERENTIAL_CONSTRAINTS.DELETE_RULE FROM information_schema.REFERENTIAL_CONSTRAINTS INNER JOIN information_schema.KEY_COLUMN_USAGE ON ( information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME = information_schema.KEY_COLUMN_USAGE.CONSTRAINT_NAME ) WHERE ( information_schema.KEY_COLUMN_USAGE.TABLE_SCHEMA = ? AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = ? )

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off,hash_join_cardinality=on,cset_narrowing=off,sargable_casefold=on

Writing a core file...
Working directory at /home/gerald/.local/share/akonadi/db_data
Resource Limits (excludes unlimited resources):
Limit                     Soft Limit           Hard Limit           Units     
Max stack size            8388608              unlimited            bytes     
Max processes             4096                 62656                processes
Max open files            3499                 3499                 files     
Max locked memory         8388608              8388608              bytes     
Max pending signals       62656                62656                signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                   
Max realtime priority     0                    0                   
Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %d

Kernel version: Linux version 6.6.120-desktop-1.mga9 (iurt@rabbit.mageia.org) (gcc (Mageia 12.3.0-3.mga9) 12.3.0, GNU ld (GNU Binutils) 2.40) #1 SMP PREEMPT_DYNAMIC Wed Jan 14 01:59:53 UTC 2026

(17:38:17) gerald  ~  > $


[doktor5000]

I can at least tell you that it's not a generic problem, just applied updates and akonadi still works normally.

Can you post the output of

Code: Select all

rpm -qa | grep -i maria | sort

[cambriz]

Thanks doktor5000 for your reply.
Did you reboot your system after this update?

I am not the only person. Unfortunately, my friend has the same problem on his Mageia system .

Code: Select all

(18:25:44) gerald  ~  > $ rpm -qa | grep -i maria | sort
lib64mariadb3-11.4.10-1.mga9
mariadb-11.4.10-1.mga9
mariadb-client-11.4.10-1.mga9
mariadb-common-11.4.10-1.mga9
mariadb-common-core-11.4.10-1.mga9
mariadb-core-11.4.10-1.mga9
mariadb-extra-11.4.10-1.mga9
perl-DBD-MariaDB-1.220.0-2.mga9
(18:25:51) gerald  ~  > $


[doktor5000]

So the update was complete.
Only similar report I found is from today: https://bugs.mageia.org/show_bug.cgi?id=35139
Just in case, do a backup of your akonadi data:

Code: Select all

akonadictl stop
cp -a ~/.local/share/akonadi ~/.local/share/akonadi-backup

Afterwards you could try a downgrade.

Did you reboot your system after this update?

Nope. But I also don't use kmail, kontact or anything else kdepim-related.

[morgano]

See that bug 35139 for possible manual fix.
Or downgrade for now to previous version.

[apprenti01]

Good evening,

Same problem!
Following yesterday's update (16/02/26), Kontact and Kmail no longer work.
Creating a new test user confirms that the problem seems to be more widespread.

Kind regards,

[persistability]

Ditto here. Since the mariadb upgrade cannot start akonadi, and the consequence of not being able to use Kontact / KMail. Thx

[morgano]

Fix hopefully in testing repo tomorrow.

@ Affected users, please then test and comment on the bug, so we can release it as update quickly.
https://bugs.mageia.org/show_bug.cgi?id=35139
-Welcome to QA

And also of course you are welcome to join QA to continue testing of various packages before we release, to improve quality of the updates!

[doktor5000]

Working again! The suggestion by Morgan Leijström 2026-02-18 07:59:30 CET, Setting skip_grant_tables=0, got it all running again. Many thanks.
His suggestion before that, 2026-02-18 20:39:25 CET, did not work.
Previously, when I tried to start akonadi, the place in the output where an error appeared was:

Code: Select all

org.kde.pim.akonadiserver:   Error text: "Lost connection to server during query QMYSQL3: Unable to execute statement"
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QString, "akonadi"))(":1", QVariant(QString, "SchemaVersionTable")))
org.kde.pim.akonadiserver:   Query: "SELECT information_schema.REFERENTIAL_CONSTRAINTS.CONSTRAINT_NAME,

....and more lines starting with information_schema.
And I didn't know where to go from there.

I notice that in the mysql.err log it says:

Code: Select all

"Version: '11.4.10-MariaDB'  socket: '/run/user/1001/akonadi/mysql.socket'  port: 0  Mageia MariaDB Server
260218  9:42:01 [ERROR] /usr/sbin/mysqld got signal 11 ;
Sorry, we probably made a mistake, and this is a bug.
Your assistance in bug reporting will enable us to fix this for the next release.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs about how to report
a bug on https://jira.mariadb.org/.
Please include the information from the server start above, to the end of the
information below."

It is dated Wed Jan 14 01:59:53, so should I do that or is it now considered solved?

[morgano]

is it now considered solved?

Upstream seem to know.
The issue is fixed in Mageia when it have been confirmed by more than one people that the update is working.
We welcome users to test and report to get our update out quickly.
https://bugs.mageia.org/show_bug.cgi?id=35139

[bitit]

i have followed https://bugs.mageia.org/show_bug.cgi?id=35139 but my address books are gone; all six vcard directories have been swallowed by the database. This is the biggest problem with Akonadi: it can't be trusted.

have you tips?

[doktor5000]

What did you do in particular from that bugreport?

But apart from restoring the database from a recent backup of ~/.local/share/akonadi what tips do you expect ?
Also have a look at https://userbase.kde.org/Akonadi#Backup
BTW contacts are stored in ~/.local/share/contacts

[bitit]

i have found a akonadi_back_up folder in the home , but if i try to restore database, the connection crash.
well i have recover my addresses directly form old database. now i need spend time for rebuilding de different addresses books
i'll do it

but isn't possible for every notification of upgrade make a preventive backup because akonadi can lose the information; should be have a way for a most strong secure protection of akonadi data system.

[doktor5000]

but isn't possible for every notification of upgrade make a preventive backup because akonadi can lose the information

Everything is possible. Feel free to report that upstream as a feature request: https://bugs.kde.org/

You can also just regularly run pimdataexporter.