[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 Resolution|NOT A BUG

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 Martin Senftleben changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 Martin Senftleben changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 --- Comment #10 from Martin Senftleben --- Sorry for not replying earlier. I did try "sudo mariadb-upgrade" and get only the following message: "Version check failed. Got the following error when calling the 'mysql' command line client ERROR 1045 (2800

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 --- Comment #9 from Maik Qualmann --- With the current MariaDB you will not be spared to carry out a "mariadb-upgrade" in the future either. Go to a terminal, become "root" and enter "mariadb-upgrade". Then digiKam should update the database schema with

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 Martin Senftleben changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #8 from Martin Senftleben

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 Maik Qualmann changed: What|Removed |Added Severity|critical|grave -- You are receiving this mail because:

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 --- Comment #6 from Maik Qualmann --- The MariaDB-10.6.x problem affects not only digiKam, but also other programs that use the Qt-MySQL driver. You can read the story at the doublicate bug report. Maik -- You are receiving this mail because: You are

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 --- Comment #5 from Maik Qualmann --- Ok, there is a problem here. MariaDB version 10.6.x is a major update, which also causes problems with the Qt-MySQL driver. The problems have already been solved, Archlinux was the pioneer because they are always ve

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 --- Comment #4 from Martin Senftleben --- If it's Mariadb, it has the version 10.6.4-1 -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 --- Comment #3 from Martin Senftleben --- Thank you, Mike, that was a helpful hint. Here is the output: "digikam.widgets: Use installed icons digikam.general: Switch to widget style: "breeze" digikam.general: AlbumWatch is disabled digikam.general: Da

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik

[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"

https://bugs.kde.org/show_bug.cgi?id=79 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment