Bug 35143 - after the last update (11.4.10-1), mariadb crashes when starting kmail
Summary: after the last update (11.4.10-1), mariadb crashes when starting kmail
Status: RESOLVED DUPLICATE of bug 35139
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-18 17:20 CET by Christian C
Modified: 2026-02-18 20:44 CET (History)
0 users

See Also:
Source RPM: mariadb3-11.4.10-1.mga9.x86_64 packages lib64dcmtk17-3.6.7-4.7.mga9.x86_64 usbmuxd-1.1.1-3.1.mga9.x86_64
CVE:
Status comment:


Attachments
Extract of journalctl log from the beginning of the plasma session (331.34 KB, application/octet-stream)
2026-02-18 17:24 CET, Christian C
Details

Description Christian C 2026-02-18 17:20:33 CET
Description of problem:

Just after having installed the last updated packages, I ran kmail which displayed empty with a message indicating that mysql/mariadb was not available.

In the attached extract of journalctl, one can see a lot of core dump related to light-locker, mysqld, akonadiserver, baloo_file, DiscoverNotifie.


Version-Release number of selected component (if applicable):
Probably 11.4.10-1.
I don't know if lib64dcmtk17-3.6.7-4.7 and usbmuxd-1.1.1-3.1 are implied.
For the moment, I have restored my previous backup.

How reproducible:
At least twice.
After the crash, I rebooted my computer to see if it changed anything.

Steps to Reproduce:
1. install the following packages lib64mariadb3-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 mariadb-11.4.10-1.mga9.x86_64 lib64dcmtk17-3.6.7-4.7.mga9.x86_64 usbmuxd-1.1.1-3.1.mga9.x86_64 lib64mariadbd19-11.4.10-1.mga9.x86_64
2. start kmail
3.
Comment 1 Christian C 2026-02-18 17:24:17 CET
Created attachment 15434 [details]
Extract of journalctl log from the beginning of the plasma session
Comment 2 sturmvogel 2026-02-18 17:40:31 CET
Please search for existing bugs before creating new ones

*** This bug has been marked as a duplicate of bug 35139 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE

Comment 3 Christian C 2026-02-18 20:44:00 CET
Sorry but this is what I did !
And I saw nothing while my keyword was mariadb.

Note You need to log in before you can comment on or make changes to this bug.