New release with a lot of fixes https://mariadb.com/docs/release-notes/community-server/11.4/11.4.10
Regular update of mariadb which brings some bugfixes https://mariadb.com/docs/release-notes/community-server/11.4/11.4.10 -------------------------------- Files in core/updates_testing: mariadb-client-11.4.10-1.mga9 mariadb-client-debuginfo-11.4.10-1.mga9 mariadb-rocks-11.4.10-1.mga9 mariadb-mroonga-debuginfo-11.4.10-1.mga9 lib64mariadbd19-11.4.10-1.mga9 lib64mariadb-embedded-devel-11.4.10-1.mga9 mariadb-core-11.4.10-1.mga9 mariadb-debuginfo-11.4.10-1.mga9 mariadb-spider-debuginfo-11.4.10-1.mga9 lib64mariadb-devel-11.4.10-1.mga9 mariadb-mroonga-11.4.10-1.mga9 mariadb-s3-engine-11.4.10-1.mga9 mariadb-connect-debuginfo-11.4.10-1.mga9 mariadb-bench-debuginfo-11.4.10-1.mga9 mariadb-feedback-debuginfo-11.4.10-1.mga9 mariadb-connect-11.4.10-1.mga9 mariadb-spider-11.4.10-1.mga9 mariadb-s3-engine-debuginfo-11.4.10-1.mga9 mariadb-extra-debuginfo-11.4.10-1.mga9 mariadb-obsolete-debuginfo-11.4.10-1.mga9 mariadb-11.4.10-1.mga9 lib64mariadb3-debuginfo-11.4.10-1.mga9 mariadb-sphinx-debuginfo-11.4.10-1.mga9 mariadb-extra-11.4.10-1.mga9 mariadb-sequence-debuginfo-11.4.10-1.mga9 mariadb-common-core-11.4.10-1.mga9 lib64mariadb3-11.4.10-1.mga9 mariadb-sphinx-11.4.10-1.mga9 mariadb-obsolete-11.4.10-1.mga9 mariadb-pam-debuginfo-11.4.10-1.mga9 mariadb-pam-11.4.10-1.mga9 mariadb-sequence-11.4.10-1.mga9 mysql-MariaDB-11.4.10-1.mga9 lib64mariadb-devel-debuginfo-11.4.10-1.mga9 mariadb-feedback-11.4.10-1.mga9 mariadb-common-11.4.10-1.mga9 mariadb-debugsource-11.4.10-1.mga9 lib64mariadbd19-debuginfo-11.4.10-1.mga9 mariadb-core-debuginfo-11.4.10-1.mga9 mariadb-bench-11.4.10-1.mga9 mariadb-common-debuginfo-11.4.10-1.mga9 lib64mariadb-embedded-devel-debuginfo-11.4.10-1.mga9 mariadb-rocks-debuginfo-11.4.10-1.mga9 SRPM: mariadb-11.4.10-1.mga9.src.rpm
Assignee: mageia => qa-bugs
MGA9-64 server Plasma Wayland on Compaq H000SB No installation issues. Ref bug 34744. # systemctl start mysqld # systemctl -l status mysqld ● mysqld.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mysqld.service; disabled; preset: disabled) Active: active (running) since Thu 2026-02-12 10:33:41 CET; 30s ago Process: 14227 ExecStartPre=/usr/sbin/mariadb-prepare-db-dir (code=exited, status=0/SUCCESS) Main PID: 14254 (mysqld) Status: "Taking your SQL requests now..." Tasks: 17 (limit: 8805) Memory: 71.8M CPU: 21.521s CGroup: /system.slice/mysqld.service └─14254 /usr/sbin/mysqld Feb 12 10:32:59 mach3.hviaene.thuis mysqld[14254]: 2026-02-12 10:32:59 0 [Note] InnoDB: log sequence number 4650706; transaction id 2027 Feb 12 10:32:59 mach3.hviaene.thuis mysqld[14254]: 2026-02-12 10:32:59 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool Feb 12 10:32:59 mach3.hviaene.thuis mysqld[14254]: 2026-02-12 10:32:59 0 [Note] CONNECT: Version 1.07.0002 March 22, 2021 Feb 12 10:32:59 mach3.hviaene.thuis mysqld[14254]: 260212 10:32:59 server_audit: MariaDB Audit Plugin version 1.4.14 STARTED. Feb 12 10:32:59 mach3.hviaene.thuis mysqld[14254]: 260212 10:32:59 server_audit: Query cache is enabled with the TABLE events. Some table reads can > Feb 12 10:33:00 mach3.hviaene.thuis mysqld[14254]: 2026-02-12 10:33:00 0 [Note] InnoDB: Buffer pool(s) load completed at 260212 10:33:00 Feb 12 10:33:41 mach3.hviaene.thuis mysqld[14254]: 2026-02-12 10:33:41 0 [Note] mysqld: Event Scheduler: Loaded 0 events Feb 12 10:33:41 mach3.hviaene.thuis mysqld[14254]: 2026-02-12 10:33:41 0 [Note] /usr/sbin/mysqld: ready for connections. Feb 12 10:33:41 mach3.hviaene.thuis mysqld[14254]: Version: '11.4.10-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 0 Mageia MariaDB Server Feb 12 10:33:41 mach3.hviaene.thuis systemd[1]: Started mysqld.service. [root@mach3 ~]# systemctl start httpd Tested by using phpmyadmin: deleting an existing test database, create a new one. In it a new table with serial field as PK, text field as unique key, plain text field and a timestamp field. Populated wit some data. All worked OK.
Whiteboard: (none) => MGA9-64-OKFlags: (none) => test_passed_mga9_64+CC: (none) => herman.viaene
Installed and tested for 2 days without issues. Tested with: - network access disabled, only using unix socket. - systemd restricted service for improved security (see below); - mysql CLI; - dbeaver-ce; - PHP scripts (e.g. phpmyadmin, nextcloud, roundcubemail, wordpress, drupal); - Qt6 applications using the QSqlMySql plugin driver. All OK. System: Mageia 9, x86_64, Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz. $ uname -a Linux marte 6.6.120-server-1.mga9 #1 SMP PREEMPT_DYNAMIC Wed Jan 14 03:15:42 UTC 2026 x86_64 GNU/Linux $ rpm -qa | grep mariadb | sort -u 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 $ systemctl status mysqld.service ● mysqld.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; preset: disabled) Drop-In: /etc/systemd/system/mysqld.service.d └─override.conf Active: active (running) since Sat 2026-02-14 10:00:21 WET; 2h 28min ago Process: 910950 ExecStartPre=/usr/sbin/mariadb-prepare-db-dir (code=exited, status=0/SUCCESS) Main PID: 910967 (mysqld) Status: "Taking your SQL requests now..." Tasks: 14 (limit: 19018) Memory: 142.4M CPU: 7.197s CGroup: /system.slice/mysqld.service └─910967 /usr/sbin/mysqld fev 14 10:00:17 marte systemd[1]: Starting mysqld.service... fev 14 10:00:17 marte mysqld[910967]: /usr/sbin/mysqld: Deprecated program name. It will be removed in a future release, use '/usr/sbin/mariadbd' instead fev 14 10:00:17 marte mysqld[910967]: 2026-02-14 10:00:17 0 [Warning] failed to retrieve the MAC address fev 14 10:00:21 marte systemd[1]: Started mysqld.service. $ cat /etc/systemd/system/mysqld.service.d/override.conf # If "skip-networking" is set in the configuration then "AF_INET AF_INET6" # should be removed from RestrictAddressFamilies and PrivateNetwork=should # be set to "yes". [Service] IPAddressDeny=any PrivateNetwork=yes PrivateUsers=yes PrivateTmp=yes PrivateDevices=yes DevicePolicy=closed UMask=0077 NoNewPrivileges=yes LockPersonality=yes MemoryDenyWriteExecute=yes RemoveIPC=yes RestrictRealtime=yes RestrictSUIDSGID=yes RestrictNamespaces=yes RestrictAddressFamilies=AF_UNIX #RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6 SystemCallArchitectures=native SystemCallFilter=@system-service @chown SystemCallFilter=~ @privileged @resources ProtectProc=invisible ProtectHome=yes ProtectHostname=yes ProtectKernelLogs=yes ProtectClock=yes ProtectControlGroups=yes ProtectKernelModules=yes ProtectKernelTunables=yes ProtectKernelLogs=yes ProtectSystem=strict AmbientCapabilities= CapabilityBoundingSet= StateDirectory=mysql RuntimeDirectory=mysqld LogsDirectory=mysqld
CC: (none) => mageia
Keywords: (none) => advisory
Validating.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2026-0012.html
Status: NEW => RESOLVEDResolution: (none) => FIXED
For two users (one reporting): Kontact / akonadi doesn't start after latest MariaDB update But not problem for all - works for doktor5000 crash log in bottom code-block in this post https://forums.mageia.org/en/viewtopic.php?t=15834#p92316 Ideas?
CC: (none) => fri
(In reply to Morgan Leijström from comment #6) > For two users (one reporting): > Kontact / akonadi doesn't start after latest MariaDB update > > But not problem for all - works for doktor5000 > > crash log in bottom code-block in this post > https://forums.mageia.org/en/viewtopic.php?t=15834#p92316 > > Ideas? I really think this should be a new bug, once said that, I get the issue in the i586 system after update mariadb and reboot for the microcode bug, before the update and reboot the service was running. I see in ~/.local/share/sddm/xorg-session.log in lxqt: /usr/bin/mysqlcheck: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-check' instead /usr/bin/mysql_upgrade: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-upgrade' instead 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' And coredumpctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages. Pass -q to turn off this notice. TIME PID UID GID SIG COREFILE EXE SIZE Tue 2026-02-17 12:34:25 CST 5712 1000 1000 SIGSEGV present /usr/sbin/mariadbd 1.0M Tue 2026-02-17 12:34:29 CST 5439 1000 1000 SIGABRT present /usr/bin/akonadiserver 584.9K Tue 2026-02-17 12:34:56 CST 6429 1000 1000 SIGSEGV present /usr/sbin/mariadbd 1.0M Tue 2026-02-17 12:34:58 CST 6424 1000 1000 SIGABRT present /usr/bin/akonadiserver 586.2K Tue 2026-02-17 12:35:29 CST 6682 1000 1000 SIGSEGV present /usr/sbin/mariadbd 1.0M Tue 2026-02-17 12:35:39 CST 6676 1000 1000 SIGABRT present /usr/bin/akonadiserver 586.0K
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".
Thanks! -> Bug 35139