Description of problem: Since the upgrade of Mariadb in version 11.4.10, the server crashes with segmentation fault when requesting the table information_schema.REFERENTIAL_CONSTRAINTS. Conséquence : Akonadi does no longer start et donc, no more KOrganizer, KMail, KAddressBook, ... Version-Release number of selected component (if applicable): 11.4.10 How reproducible: when kde starts Steps to Reproduce: 1.Launch server : /usr/sbin/mysqld --defaults-file=${HOME}/.local/share/akonadi/mysql.conf --datadir=${HOME}/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid 2.Launch client : mariadb -u root --socket=/run/user/1000/akonadi/mysql.socket 3.Type the request : select count(*) from information_schema.REFERENTIAL_CONSTRAINTS; Fix: downgrade to 11.4.9
Copy answer from https://bugs.mageia.org/show_bug.cgi?id=35112#c8 This warning in the update of the package could be related The initscript used to start mariadb has been reverted to use the one shipped by MariaDB. This means the following changes: * The generation of the initial system mysql database is now done when mariadb is started from the initscript and only if the /var/lib/mysql/mysql directory is empty (mariadb-install-db). Previousely this was quite hidden and silently done at (rpm) install time. As a consequence to this change you may have to perform some manual tasks to upgrade the mariadb system database and such. So, doing something like this might help you: systemctl stop mysqld.service TMPDIR=/var/tmp mariadb-install-db systemctl start mysqld.service mariadb-upgrade --skip-write-binlog mariadb-tzinfo-to-sql /usr/share/zoneinfo | mariadb -D mysql NOTE: Most mysql commands have equivalents with mariadb prefix. Old mysql commands will show warnings and will be removed in later releases. This also affects the main thread which will be called "mariadb-safe" instead of "mysql-safe".
Assignee: bugsquad => mageiaCC: (none) => fri
In forum crash log in bottom code-block in this post https://forums.mageia.org/en/viewtopic.php?t=15834#p92316
Summary: Mariadb crashe, Akonadi ne démarre pas => MariaDB 11.4.10 update breaks installs, i.e Akonadi and Kontact - need manual intervention
Added akonadi just in case the solution could be an adust in akonadi
Source RPM: (none) => mariadb,akonadiCC: (none) => j.alberto.vc
*** Bug 35140 has been marked as a duplicate of this bug. ***
CC: (none) => lloyd.osten
Lloyd I added you to CC list of this bug
The procedure in comment 1 did not help me with the issue in my laptop, mariadb and akonadiserver still coredump like in bug 35112 comment 7
Hello, Might looks be related to this. https://bugs.kde.org/show_bug.cgi?id=515873
Interesting there: Setting skip_grant_tables=0 (default was just skip_grant_tables) in ~/.local/share/akonadi/mysql.conf also makes akonadi work again. Does that work for us?
can someone post the contents of ~/.local/share/akonadi/mysql.conf does it also crash, if you ommit the defaults file?
Content of my ~/.local/share/akonadi/mysql.conf : # # Global Akonadi MySQL server settings, # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf # # Based on advice by Kris Köhntopp <kris@mysql.com> # [mysqld] # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled # sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat # sql_mode=strict_trans_tables # DEBUGGING: # log all queries, useful for debugging but generates an enormous amount of data # log=mysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) # log_slow_queries=mysql.slow # long_query_time=1 # log queries not using indices, debug only, disable for production use # log_queries_not_using_indexes=1 # # mesure database size and adjust innodb_buffer_pool_size # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema"); # NOTES: # Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) #expire_logs_days=3 #sync_bin_log=0 # Use UTF-8 encoding for tables character_set_server=utf8 collation_server=utf8_general_ci # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # memory pool InnoDB uses to store data dictionary information and other internal data structures (default:8M) # Deprecated in MySQL >= 5.6.3, removed in 5.7 (works in MariaDB) # innodb_additional_mem_pool_size=8M # memory buffer InnoDB uses to cache data and indexes of its tables (default:128M) # Larger values means less I/O innodb_buffer_pool_size=128M # Create a .ibd file for each table (default:0) innodb_file_per_table=1 # Write out the log buffer to the log file at each commit (default:1) innodb_flush_log_at_trx_commit=2 # Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin) # larger values means less I/O innodb_log_buffer_size=1M # Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery. innodb_log_file_size=64M # # error log file name, relative to datadir (default:hostname.err) log_error=mysql.err # print warnings and connection errors (default:1) log_warnings=2 # Convert table named to lowercase lower_case_table_names=1 # Maximum size of one packet or any generated/intermediate string. (default:1M) max_allowed_packet=32M # Maximum simultaneous connections allowed (default:100) max_connections=256 # The two options below make no sense with prepared statements and/or transactions # (make sense when having the same query multiple times) # Memory allocated for caching query results (default:0 (disabled)) query_cache_size=2048M query_cache_limit=1024M # Do not cache results (default:1) query_cache_type=0 # Do not use the privileges mechanisms skip_grant_tables # Do not listen for TCP/IP connections at all skip_networking # The number of open tables for all threads. (default:64) table_open_cache=200 # How many threads the server should cache for reuse (default:0) thread_cache_size=3 # wait 365d before dropping the DB connection (default:8h) wait_timeout=31536000 # We use InnoDB, so don't let MyISAM eat up memory key_buffer_size=16K [client] default-character-set=utf8
It seems to have an upstream fix: https://github.com/MariaDB/server/commit/87309d3d4bb8f48910d05b0ca5ee989bcdd6b053
CC: (none) => yves.brungard
Thanks. This fix is short and I'm going to patch it tonight.
Great, thanks for quick handling.
Summary: MariaDB 11.4.10 update breaks installs, i.e Akonadi and Kontact - need manual intervention => MariaDB 11.4.10 update breaks installs, i.e Akonadi, Kontact, Kmail - need manual intervention
I tried the fix by changing skip_grant_tables to skip_grant_tables=0. While it may be a temporary workaround, it did work. I'll be applying the patch as soon as it's released.
Build is running...
I can replicate the crash. I will be able to test the updates. $ rpm -qa | grep mariadb lib64mariadb3-11.4.9-1.mga9 mariadb-client-11.4.9-1.mga9 mariadb-common-11.4.9-1.mga9 mariadb-common-core-11.4.9-1.mga9 mariadb-core-11.4.9-1.mga9 mariadb-11.4.9-1.mga9 mariadb-extra-11.4.9-1.mga9 $ akonadictl status Akonadi Control: running Akonadi Server: running 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 # LANGUAGE=C urpmi --auto-select To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Updates") lib64mariadb3 11.4.10 1.mga9 x86_64 lib64pq5 15.16 1.mga9 x86_64 mariadb 11.4.10 1.mga9 x86_64 mariadb-client 11.4.10 1.mga9 x86_64 mariadb-common 11.4.10 1.mga9 x86_64 mariadb-common-core 11.4.10 1.mga9 x86_64 mariadb-core 11.4.10 1.mga9 x86_64 mariadb-extra 11.4.10 1.mga9 x86_64 usbmuxd 1.1.1 3.1.mga9 x86_64 78KB of additional disk space will be used. 20MB of packages will be retrieved. Proceed with the installation of the 9 packages? (Y/n) installing mariadb-common-11.4.10-1.mga9.x86_64.rpm lib64mariadb3-11.4.10-1.mga9.x86_64.rpm mariadb-core-11.4.10-1.mga9.x86_64.rpm mariadb-extra-11.4.10-1.mga9.x86_64.rpm lib64pq5-15.16-1.mga9.x86_64.rpm mariadb-common-core-11.4.10-1.mga9.x86_64.rpm mariadb-11.4.10-1.mga9.x86_64.rpm usbmuxd-1.1.1-3.1.mga9.x86_64.rpm mariadb-client-11.4.10-1.mga9.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ######################################### 1/9: lib64mariadb3 ######################################### 2/9: mariadb-client ######################################### 3/9: mariadb-common ######################################### 4/9: mariadb-common-core ######################################### 5/9: mariadb-core ######################################### 6/9: mariadb-extra ######################################### 7/9: mariadb ######################################### 8/9: usbmuxd ######################################### 9/9: lib64pq5 ######################################### 1/9: removing mariadb-11.4.9-1.mga9.x86_64 ######################################### 2/9: removing mariadb-core-11.4.9-1.mga9.x86_64 ######################################### 3/9: removing mariadb-extra-11.4.9-1.mga9.x86_64 ######################################### 4/9: removing mariadb-common-core-11.4.9-1.mga9.x86_64 ######################################### 5/9: removing mariadb-common-11.4.9-1.mga9.x86_64 ######################################### 6/9: removing mariadb-client-11.4.9-1.mga9.x86_64 ######################################### 7/9: removing lib64mariadb3-11.4.9-1.mga9.x86_64 ######################################### 8/9: removing usbmuxd-1.1.1-3.mga9.x86_64 ######################################### 9/9: removing lib64pq5-15.15-1.mga9.x86_64 ######################################### ---------------------------------------------------------------------- More information on package mariadb-11.4.10-1.mga9.x86_64 NOTE: MariaDB is installed without root password, it is recommended to set the root password with the following command as soon as possible: # mysql_secure_installation press enter at each question except the new root password. The initscript used to start mariadb has been reverted to use the one shipped by MariaDB. This means the following changes: * The generation of the initial system mysql database is now done when mariadb is started from the initscript and only if the /var/lib/mysql/mysql directory is empty (mariadb-install-db). Previousely this was quite hidden and silently done at (rpm) install time. As a consequence to this change you may have to perform some manual tasks to upgrade the mariadb system database and such. So, doing something like this might help you: systemctl stop mysqld.service TMPDIR=/var/tmp mariadb-install-db systemctl start mysqld.service mariadb-upgrade --skip-write-binlog mariadb-tzinfo-to-sql /usr/share/zoneinfo | mariadb -D mysql NOTE: Most mysql commands have equivalents with mariadb prefix. Old mysql commands will show warnings and will be removed in later releases. This also affects the main thread which will be called "mariadb-safe" instead of "mysql-safe". ---------------------------------------------------------------------- # systemctl start mysqld.service # mariadb-upgrade --skip-write-binlog This installation of MariaDB is already upgraded to 11.4.10-MariaDB. There is no need to run mariadb-upgrade again. You can use --force if you still want to run mariadb-upgrade # systemctl status mysqld.service ● mysqld.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mysqld.service; disabled; preset: disabled) Active: active (running) since Wed 2026-02-18 14:56:51 WET; 15s ago Process: 18843 ExecStartPre=/usr/sbin/mariadb-prepare-db-dir (code=exited, status=0/SUCCESS) Main PID: 18912 (mysqld) Status: "Taking your SQL requests now..." Tasks: 13 (limit: 4657) Memory: 125.0M CPU: 1.980s CGroup: /system.slice/mysqld.service └─18912 /usr/sbin/mysqld fev 18 14:56:50 jupiter-vm-mageia-9 mysqld[18912]: 2026-02-18 14:56:50 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. fev 18 14:56:50 jupiter-vm-mageia-9 mysqld[18912]: 2026-02-18 14:56:50 0 [Note] InnoDB: log sequence number 45616; transaction id 14 fev 18 14:56:50 jupiter-vm-mageia-9 mysqld[18912]: 2026-02-18 14:56:50 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool fev 18 14:56:50 jupiter-vm-mageia-9 mysqld[18912]: 2026-02-18 14:56:50 0 [Note] InnoDB: Buffer pool(s) load completed at 260218 14:56:50 fev 18 14:56:50 jupiter-vm-mageia-9 mysqld[18912]: 260218 14:56:50 server_audit: MariaDB Audit Plugin version 1.4.14 STARTED. fev 18 14:56:50 jupiter-vm-mageia-9 mysqld[18912]: 260218 14:56:50 server_audit: Query cache is enabled with the TABLE events. Some table reads can be veiled.2026-02-18 14:56:50 0 [Note] Plugin 'wsrep-provider' is disabled. fev 18 14:56:51 jupiter-vm-mageia-9 mysqld[18912]: 2026-02-18 14:56:51 0 [Note] mysqld: Event Scheduler: Loaded 0 events fev 18 14:56:51 jupiter-vm-mageia-9 mysqld[18912]: 2026-02-18 14:56:51 0 [Note] /usr/sbin/mysqld: ready for connections. fev 18 14:56:51 jupiter-vm-mageia-9 mysqld[18912]: Version: '11.4.10-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 0 Mageia MariaDB Server fev 18 14:56:51 jupiter-vm-mageia-9 systemd[1]: Started mysqld.service. $ rpm -qa | grep mariadb lib64mariadb3-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 mariadb-11.4.10-1.mga9 $ 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 $ akonadictl start org.kde.pim.akonadictl: Starting Akonadi Server... org.kde.pim.akonadictl: done. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) $ org.kde.pim.akonadiserver: Starting up the Akonadi Server... /usr/bin/mysqlcheck: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-check' instead akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontable OK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelation OK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK /usr/bin/mysql_upgrade: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-upgrade' instead This installation of MariaDB is already upgraded to 11.4.9-MariaDB. There is no need to run mariadb-upgrade again for 11.4.10-MariaDB, because they're both 11.4. You can use --force if you still want to run mariadb-upgrade org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: DB initializer done org.kde.pim.akonadiserver: DATABASE ERROR: org.kde.pim.akonadiserver: Error code: "2013" org.kde.pim.akonadiserver: DB error: "Lost connection to server during query" 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, 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 = :0 AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = :1 )" org.kde.pim.akonadiserver: DATABASE ERROR: org.kde.pim.akonadiserver: Error code: "2006" org.kde.pim.akonadiserver: DB error: "Server has gone away" org.kde.pim.akonadiserver: Error text: "Server has gone away QMYSQL3: Unable to execute statement" org.kde.pim.akonadiserver: Values: QMap((":0", QVariant(QString, "akonadi"))(":1", QVariant(QString, "ResourceTable"))) org.kde.pim.akonadiserver: Query: "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 = :0 AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = :1 )" org.kde.pim.akonadiserver: DATABASE ERROR: org.kde.pim.akonadiserver: Error code: "2006" org.kde.pim.akonadiserver: DB error: "Server has gone away" org.kde.pim.akonadiserver: Error text: "Server has gone away QMYSQL3: Unable to execute statement" org.kde.pim.akonadiserver: Values: QMap((":0", QVariant(QString, "akonadi"))(":1", QVariant(QString, "CollectionTable"))) org.kde.pim.akonadiserver: Query: "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 = :0 AND information_schema.KEY_COLUMN_USAGE.TABLE_NAME = :1 )" terminate called after throwing an instance of 'Akonadi::Server::DbException' what(): Failed to query index Sql error: Server has gone away QMYSQL: Unable to execute query Query: SHOW INDEXES FROM CollectionTable WHERE `Key_name` = 'CollectionTable_parentAndNameIndex' org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadiserver" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' crashed! 1 restarts left. <SNIP repeated crashes> $ coredumpctl TIME PID UID GID SIG COREFILE EXE SIZE Wed 2026-02-18 14:59:28 WET 19887 1000 1000 SIGSEGV none /usr/sbin/mariadbd - Wed 2026-02-18 14:59:28 WET 19876 1000 1000 SIGABRT none /usr/bin/akonadiserver - Wed 2026-02-18 14:59:31 WET 20041 1000 1000 SIGSEGV none /usr/sbin/mariadbd - Wed 2026-02-18 14:59:31 WET 20036 1000 1000 SIGABRT none /usr/bin/akonadiserver - Wed 2026-02-18 14:59:34 WET 20264 1000 1000 SIGSEGV none /usr/sbin/mariadbd - Wed 2026-02-18 14:59:34 WET 20261 1000 1000 SIGABRT none /usr/bin/akonadiserver - Wed 2026-02-18 14:59:49 WET 20377 1000 1000 SIGSEGV none /usr/sbin/mariadbd - Wed 2026-02-18 14:59:50 WET 20371 1000 1000 SIGABRT none /usr/bin/akonadiserver - Wed 2026-02-18 14:59:51 WET 20559 1000 1000 SIGSEGV none /usr/sbin/mariadbd - Wed 2026-02-18 14:59:51 WET 20556 1000 1000 SIGABRT none /usr/bin/akonadiserver - Wed 2026-02-18 14:59:52 WET 20602 1000 1000 SIGSEGV none /usr/sbin/mariadbd - Wed 2026-02-18 14:59:52 WET 20598 1000 1000 SIGABRT none /usr/bin/akonadiserver -
CC: (none) => mageia
build done and uploaded, waiting for the sync :)
*** Bug 35143 has been marked as a duplicate of this bug. ***
CC: (none) => bugzzzz
RPMS: i586: libmariadb-devel-11.4.10-1.1.mga9.i586.rpm libmariadb-embedded-devel-11.4.10-1.1.mga9.i586.rpm libmariadb3-11.4.10-1.1.mga9.i586.rpm libmariadbd19-11.4.10-1.1.mga9.i586.rpm mariadb-11.4.10-1.1.mga9.i586.rpm mariadb-bench-11.4.10-1.1.mga9.i586.rpm mariadb-client-11.4.10-1.1.mga9.i586.rpm mariadb-common-11.4.10-1.1.mga9.i586.rpm mariadb-common-core-11.4.10-1.1.mga9.i586.rpm mariadb-connect-11.4.10-1.1.mga9.i586.rpm mariadb-core-11.4.10-1.1.mga9.i586.rpm mariadb-extra-11.4.10-1.1.mga9.i586.rpm mariadb-feedback-11.4.10-1.1.mga9.i586.rpm mariadb-mroonga-11.4.10-1.1.mga9.i586.rpm mariadb-obsolete-11.4.10-1.1.mga9.i586.rpm mariadb-pam-11.4.10-1.1.mga9.i586.rpm mariadb-s3-engine-11.4.10-1.1.mga9.i586.rpm mariadb-sequence-11.4.10-1.1.mga9.i586.rpm mariadb-sphinx-11.4.10-1.1.mga9.i586.rpm mariadb-spider-11.4.10-1.1.mga9.i586.rpm mysql-MariaDB-11.4.10-1.1.mga9.i586.rpm x86_64: lib64mariadb-devel-11.4.10-1.1.mga9.x86_64.rpm lib64mariadb-embedded-devel-11.4.10-1.1.mga9.x86_64.rpm lib64mariadb3-11.4.10-1.1.mga9.x86_64.rpm lib64mariadbd19-11.4.10-1.1.mga9.x86_64.rpm mariadb-11.4.10-1.1.mga9.x86_64.rpm mariadb-bench-11.4.10-1.1.mga9.x86_64.rpm mariadb-client-11.4.10-1.1.mga9.x86_64.rpm mariadb-common-11.4.10-1.1.mga9.x86_64.rpm mariadb-common-core-11.4.10-1.1.mga9.x86_64.rpm mariadb-connect-11.4.10-1.1.mga9.x86_64.rpm mariadb-core-11.4.10-1.1.mga9.x86_64.rpm mariadb-extra-11.4.10-1.1.mga9.x86_64.rpm mariadb-feedback-11.4.10-1.1.mga9.x86_64.rpm mariadb-mroonga-11.4.10-1.1.mga9.x86_64.rpm mariadb-obsolete-11.4.10-1.1.mga9.x86_64.rpm mariadb-pam-11.4.10-1.1.mga9.x86_64.rpm mariadb-rocks-11.4.10-1.1.mga9.x86_64.rpm mariadb-s3-engine-11.4.10-1.1.mga9.x86_64.rpm mariadb-sequence-11.4.10-1.1.mga9.x86_64.rpm mariadb-sphinx-11.4.10-1.1.mga9.x86_64.rpm mariadb-spider-11.4.10-1.1.mga9.x86_64.rpm mysql-MariaDB-11.4.10-1.1.mga9.x86_64.rpm SRPM: mariadb-11.4.10-1.1.mga9
Assignee: mageia => qa-bugsStatus: NEW => ASSIGNED
Source RPM: mariadb,akonadi => mariadbKeywords: (none) => advisory
RH i586 Installed with other packages installing //home/katnatek/qa-testing/i586/mariadb-common-11.4.10-1.1.mga9.i586.rpm //home/katnatek/qa-testing/i586/mariadb-11.4.10-1.1.mga9.i586.rpm //home/katnatek/qa-testing/i586/mariadb-extra-11.4.10-1.1.mga9.i586.rpm /var/cache/urpmi/rpms/vim-enhanced-9.1.2148-1.mga9.i586.rpm //home/katnatek/qa-testing/i586/mariadb-common-core-11.4.10-1.1.mga9.i586.rpm //home/katnatek/qa-testing/i586/libmariadb3-11.4.10-1.1.mga9.i586.rpm /var/cache/urpmi/rpms/vim-minimal-9.1.2148-1.mga9.i586.rpm /var/cache/urpmi/rpms/vim-common-9.1.2148-1.mga9.i586.rpm //home/katnatek/qa-testing/i586/mariadb-core-11.4.10-1.1.mga9.i586.rpm //home/katnatek/qa-testing/i586/mariadb-client-11.4.10-1.1.mga9.i586.rpm Preparing... ####################################################################################### 1/10: vim-common ####################################################################################### 2/10: libmariadb3 ####################################################################################### 3/10: mariadb-client ####################################################################################### 4/10: mariadb-common ####################################################################################### 5/10: mariadb-common-core ####################################################################################### 6/10: mariadb-extra ####################################################################################### 7/10: mariadb-core ####################################################################################### 8/10: mariadb ####################################################################################### 9/10: vim-enhanced ####################################################################################### 10/10: vim-minimal ####################################################################################### 1/10: removing mariadb-11.4.10-1.mga9.i586 ####################################################################################### 2/10: removing mariadb-core-11.4.10-1.mga9.i586 ####################################################################################### 3/10: removing mariadb-extra-11.4.10-1.mga9.i586 ####################################################################################### 4/10: removing mariadb-common-core-11.4.10-1.mga9.i586 ####################################################################################### 5/10: removing mariadb-common-11.4.10-1.mga9.i586 ####################################################################################### 6/10: removing mariadb-client-11.4.10-1.mga9.i586 ####################################################################################### 7/10: removing vim-enhanced-9.1.1552-1.mga9.i586 ####################################################################################### 8/10: removing vim-common-9.1.1552-1.mga9.i586 ####################################################################################### 9/10: removing libmariadb3-11.4.10-1.mga9.i586 ####################################################################################### 10/10: removing vim-minimal-9.1.1552-1.mga9.i586 ####################################################################################### Close session and start again ps fax , shows akonadi start 24574 ? Sl 0:00 \_ /usr/bin/akonadi_control 24591 ? Sl 0:00 | \_ /usr/bin/akonadiserver 24607 ? Sl 0:19 | | \_ /usr/sbin/mysqld --defaults-file=/home/katnatek/.local/share/akonadi/mysql. 24759 ? Rl 0:00 | \_ /usr/bin/akonadi_akonotes_resource --identifier akonadi_akonotes_resource_0 24760 ? Rl 0:00 | \_ /usr/bin/akonadi_akonotes_resource --identifier akonadi_akonotes_resource_1 24761 ? Rl 0:00 | \_ /usr/bin/akonadi_birthdays_resource --identifier akonadi_birthdays_resource 24762 ? Rl 0:00 | \_ /usr/bin/akonadi_contacts_resource --identifier akonadi_contacts_resource_0 24763 ? Rl 0:00 | \_ /usr/bin/akonadi_contacts_resource --identifier akonadi_contacts_resource_1 24764 ? Rl 0:00 | \_ /usr/bin/akonadi_ical_resource --identifier akonadi_ical_resource_0 24765 ? Rl 0:00 | \_ /usr/bin/akonadi_ical_resource --identifier akonadi_ical_resource_1 24766 ? Rl 0:00 | \_ /usr/bin/akonadi_indexing_agent --identifier akonadi_indexing_agent 24767 ? Rl 0:00 | \_ /usr/bin/akonadi_maildir_resource --identifier akonadi_maildir_resource_0 24768 ? Rl 0:00 | \_ /usr/bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_agent 24772 ? Rl 0:00 | \_ /usr/bin/akonadi_migration_agent --identifier akonadi_migration_agent 24773 ? R 0:00 | \_ /usr/bin/akonadi_newmailnotifier_agent --identifier akonadi_newmailnotifier_age 24776 ? R 0:00 | \_ /usr/bin/akonadi_notes_agent --identifier akonadi_notes_agent Looks good
The latest packages fixed the akonadi crash. $ uname -a Linux jupiter-vm-mageia-9 6.6.120-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Wed Jan 14 01:59:53 UTC 2026 x86_64 GNU/Linux $ rpm -qa | grep mariadb | sort lib64mariadb3-11.4.10-1.1.mga9 mariadb-11.4.10-1.1.mga9 mariadb-client-11.4.10-1.1.mga9 mariadb-common-11.4.10-1.1.mga9 mariadb-common-core-11.4.10-1.1.mga9 mariadb-core-11.4.10-1.1.mga9 mariadb-extra-11.4.10-1.1.mga9 $ akonadictl status Akonadi Control: running Akonadi Server: running 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
CC: j.alberto.vc => (none)
I think is good but if need other test please remove OKs
CC: (none) => andrewsfarmWhiteboard: (none) => MGA9-64-OK,MGA9-32-OK
Advisory: Updated mariadb package fix crashes not using grant tables: The latest update introduced a bug which makes mariadb crash in case it was started with skip-grant-tables. E.g. akonadi uses mariadb as backend and does not use the rights management. This update fixes the issue. ------------------------------------- Files in core/updates_testing: RPMS: i586: libmariadb-devel-11.4.10-1.1.mga9.i586.rpm libmariadb-embedded-devel-11.4.10-1.1.mga9.i586.rpm libmariadb3-11.4.10-1.1.mga9.i586.rpm libmariadbd19-11.4.10-1.1.mga9.i586.rpm mariadb-11.4.10-1.1.mga9.i586.rpm mariadb-bench-11.4.10-1.1.mga9.i586.rpm mariadb-client-11.4.10-1.1.mga9.i586.rpm mariadb-common-11.4.10-1.1.mga9.i586.rpm mariadb-common-core-11.4.10-1.1.mga9.i586.rpm mariadb-connect-11.4.10-1.1.mga9.i586.rpm mariadb-core-11.4.10-1.1.mga9.i586.rpm mariadb-extra-11.4.10-1.1.mga9.i586.rpm mariadb-feedback-11.4.10-1.1.mga9.i586.rpm mariadb-mroonga-11.4.10-1.1.mga9.i586.rpm mariadb-obsolete-11.4.10-1.1.mga9.i586.rpm mariadb-pam-11.4.10-1.1.mga9.i586.rpm mariadb-s3-engine-11.4.10-1.1.mga9.i586.rpm mariadb-sequence-11.4.10-1.1.mga9.i586.rpm mariadb-sphinx-11.4.10-1.1.mga9.i586.rpm mariadb-spider-11.4.10-1.1.mga9.i586.rpm mysql-MariaDB-11.4.10-1.1.mga9.i586.rpm x86_64: lib64mariadb-devel-11.4.10-1.1.mga9.x86_64.rpm lib64mariadb-embedded-devel-11.4.10-1.1.mga9.x86_64.rpm lib64mariadb3-11.4.10-1.1.mga9.x86_64.rpm lib64mariadbd19-11.4.10-1.1.mga9.x86_64.rpm mariadb-11.4.10-1.1.mga9.x86_64.rpm mariadb-bench-11.4.10-1.1.mga9.x86_64.rpm mariadb-client-11.4.10-1.1.mga9.x86_64.rpm mariadb-common-11.4.10-1.1.mga9.x86_64.rpm mariadb-common-core-11.4.10-1.1.mga9.x86_64.rpm mariadb-connect-11.4.10-1.1.mga9.x86_64.rpm mariadb-core-11.4.10-1.1.mga9.x86_64.rpm mariadb-extra-11.4.10-1.1.mga9.x86_64.rpm mariadb-feedback-11.4.10-1.1.mga9.x86_64.rpm mariadb-mroonga-11.4.10-1.1.mga9.x86_64.rpm mariadb-obsolete-11.4.10-1.1.mga9.x86_64.rpm mariadb-pam-11.4.10-1.1.mga9.x86_64.rpm mariadb-rocks-11.4.10-1.1.mga9.x86_64.rpm mariadb-s3-engine-11.4.10-1.1.mga9.x86_64.rpm mariadb-sequence-11.4.10-1.1.mga9.x86_64.rpm mariadb-sphinx-11.4.10-1.1.mga9.x86_64.rpm mariadb-spider-11.4.10-1.1.mga9.x86_64.rpm mysql-MariaDB-11.4.10-1.1.mga9.x86_64.rpm SRPM: mariadb-11.4.10-1.1.mga9
After the last update : - lib64dcmtk17-3.6.7-4.7.mga9.x86_64 - lib64mariadb3-11.4.10-1.mga9.x86_64 - lib64mariadbd19-11.4.10-1.mga9.x86_64 - lib64pq5-15.16-1.mga9.x86_64 - mariadb-11.4.10-1.mga9.x86_64 - mariadb-client-11.4.10-1.mga9.x86_64 - mariadb-common-11.4.10-1.mga9.x86_64 - mariadb-common-core-11.4.10-1.mga9.x86_64 - mariadb-core-11.4.10-1.mga9.x86_64 - mariadb-extra-11.4.10-1.mga9.x86_64 - microcode-0.20260210-1.mga9.nonfree.noarch - postgresql15-15.16-1.mga9.x86_64 - postgresql15-plpgsql-15.16-1.mga9.x86_64 - postgresql15-server-15.16-1.mga9.x86_64 - usbmuxd-1.1.1-3.1.mga9.x86_64 - vim-common-9.1.2148-1.mga9.x86_64 - vim-enhanced-9.1.2148-1.mga9.x86_64 - vim-minimal-9.1.2148-1.mga9.x86_64 kmail still crashes with akonadi core dump. See attachment.
Created attachment 15435 [details] Traces produced in the console when kmail is started twice from the command line
Created attachment 15436 [details] 2 extracts of journalctl at crash time : one for each kmail run
Attachment 15435 description: Traces produced in the console when kmail twice is started from the command line => Traces produced in the console when kmail is started twice from the command line
The last version 11.4.10-1.1 proposed by Marc Krämer 2026-02-20 00:13:58 CET did not installed at févr. 20 11:58:06 when I ran the update. Is it a MCC issue or something else ?
And there is something weird in the MCC. The old version (11.4.10-1) mariadb packages are quoted and have a green arrow which normally is used to point out new versions. If I try to install them, I get the message "you need to select packages first". See the screenshot in attachment. My repository is : http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/9/x86_64/media/nonfree/updates/
This does not look good: /usr/bin/mysql_upgrade: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-upgrade' instead Reading datadir from the MariaDB server failed. Got the following error when executing the 'mysql' command line client ERROR 1049 (42000): Unknown database 'mysql' FATAL ERROR: Upgrade failed We should rename/patch kmail to use the newer command. (in mga10 mysql-commands have been removed) Why is the database mysql missing? I'm not sure if this causes the crash.
@Christian: you need to enable updates_testing. The updated package is not yet released
Created attachment 15437 [details] screenshot of MCC when I try to update mariadb packages
ok, thanks.
@Christian: As root, run "drakrpm-edit-media --expert" to activate the testing repos and set them for updates. There are other packages under test in those repos, so when you go after updates make sure to remove the flag from those other than the ones listed in comment 24. Once you have those updates, it's best to de-activate the testing repos again from MCC, so you don't get other untested updates in the future. (You can leave the testing flag there.)
Thanks, it's done. 11.4.10-1.1 seems ok for me. No more crash :-)
we should push this to updates.
The issue here is beyond me. I just assured mariadb does it's usual database server functions.
CC: (none) => herman.viaene
@Herman: We have a few people, which already tested. The patch is only 3 lines - I guess we can move it.
Validating.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2026-0014.html
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED