| Summary: | digiKam-MySQL-MariaDB crash | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Michel Ghelein <michel.ghelein> |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.2.0 | |
| Sentry Crash Report: | |||
| Attachments: | log generated by DebugView and copy screen of errors displayed | ||
I think we will not be able to solve the problem the start of the MariaDB server ("C:/Program Files/MariaDB 10.5/bin/mysqld.exe") crashes. The * .pdb files are not important, it tries to find the debug files.
Maik
The exit code is 80000003, this corresponds e.g. this entry in the bugtracker: https://jira.mariadb.org/browse/MDEV-23432 Maik The error code could also indicate a defective database. Then you would have to try to create a new database. We have a similar case with bug 429963. At the end we give the MySQL server 5 seconds to shut down before it is killed. This time may be too short. I will increase the waiting time. Maik Git commit 2334d832f1e17a177a18a27557ef05ec930b6b62 by Maik Qualmann. Committed on 12/12/2020 at 05:51. Pushed by mqualmann into branch 'master'. more time for the MySQL server to shut down Related: bug 429963 M +1 -1 core/libs/database/server/databaseserver.cpp https://invent.kde.org/graphics/digikam/commit/2334d832f1e17a177a18a27557ef05ec930b6b62 Read Bug 429963 (https://bugs.kde.org/show_bug.cgi?id=429963#c18). Unfortunately you will then have to create a new database. Maik Michel, Stable digiKam 7.4.0 Windows Installer is published. Please check if problem is reproducible. Thanks in advance Gilles Caulier @Michel digiKam 8.0.0 is out. Problem still reproducible ? Best regards Gilles Caulier I don’t use anymore digikam Sorry Rads Michel Ghelein Tel: 06.30.04.66.17 Michel.ghelein@sfr.fr > Le 19 avr. 2023 à 16:52, bugzilla_noreply@kde.org a écrit : > > https://bugs.kde.org/show_bug.cgi?id=430277 > > --- Comment #7 from caulier.gilles@gmail.com --- > @Michel > > digiKam 8.0.0 is out. Problem still reproducible ? > > Best regards > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. *** This bug has been marked as a duplicate of bug 429963 *** Fixed with 429963 |
Created attachment 134019 [details] log generated by DebugView and copy screen of errors displayed SUMMARY Digikam-MySQL-digikam.databaseserver: Exit code: -2147483645 digikam.databaseserver: Process error: "Process crashed" digikam.databaseserver: Cannot start internal database server Although it indicated that it is necessary to change the type of database, Digikam crashes and does not offer the possibility to do so. STEPS TO REPRODUCE Not know how reproduce on another platform OBSERVED RESULT Digikam crashed. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The 1st errors reported in DebugView are : C:\Program Files\MariaDB 10.5\bin\ucrtbase.pdb - file not found ... ... ucrtbase.pdb - file not found C:\Program Files\MariaDB 10.5\bin\ntdll.pdb - file not found ... ... ntdll.pdb - file not found C:\Program Files\MariaDB 10.5\bin\kernel32.pdb - file not found ... ... kernel32.pdb - file not found Note : Yesterday Digikam was working fine in this configuration. The only notable change was the installation today of the Windows cumulative KB4592438