https://bugs.kde.org/show_bug.cgi?id=430277
Bug ID: 430277
Summary: Digikam-MySQL-MariaDB crashe
Product: digikam
Version: 7.2.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: crash
Priority: NOR
Component: Database-Mysql
Assignee: digikam-bugs-n...@kde.org
Reporter: michel.ghel...@sfr.fr
Target Milestone: ---
Created attachment 134019
--> https://bugs.kde.org/attachment.cgi?id=134019&action=edit
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
--
You are receiving this mail because:
You are watching all bug changes.
