| Summary: | digiKam 8.6.0 Fails to Use Existing MySQL Database (Works in 8.4.0) | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | ALM <alam> |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | critical | CC: | 70tas, caulier.gilles, jmunoz, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
ALM
2025-06-11 13:58:12 UTC
Try to use "127.0.0.1" instead "localhost" in the settings... (In reply to caulier.gilles from comment #1) > Try to use "127.0.0.1" instead "localhost" in the settings... Thanks tried "127.0.0.1" instead "localhost" as suggested but no avail! Ah sorry, it's an internal mariadb server not a local server used. Install debugview and follow the instructions to capture the debug trace from the application at startup: https://www.digikam.org/contribute/#windows-host *** Bug 504717 has been marked as a duplicate of this bug. *** We no longer test with MySQL, only MariaDB. MariaDB is no longer available on Linux, and we only use MariaDB on Windows, too. The DebugView log is urgently needed here to see if we can fix anything. Maik (In reply to Maik Qualmann from comment #5) > We no longer test with MySQL, only MariaDB. MariaDB is no longer available > on Linux, and we only use MariaDB on Windows, too. The DebugView log is > urgently needed here to see if we can fix anything. > > Maik Thanks for the clarification, Maik — that finally makes the issue clear. I had been using MySQL Server 8.0 with digiKam 8.6.0 (which worked fine with 8.4.0), but ran into repeated schema creation failures and DBVersion errors. After days of troubleshooting, I’ve now fully uninstalled MySQL and will proceed with MariaDB as recommended. Kindly consider adding a visible notice in the application UI and on the digiKam website/docs stating that MySQL is no longer supported or tested. The setup wizard still lists "MySQL Server" as an option, which is misleading. This cost me over 5 days of retrying every possible configuration, assuming MySQL was still valid. I appreciate your and Gilles’ clarifications, and I’ll retest using MariaDB 10.6 or 10.11. I’ll share DebugView logs if any issues persist. Thanks again! A DebugView log of the MySQL error would be really helpful so we can fix it. For an internal MySQL server, only MariaDB can be used, since digiKam manages the server itself. For an external MySQL database, it would still be good if MySQL were working. Maik (In reply to Maik Qualmann from comment #5) > We no longer test with MySQL, only MariaDB. MariaDB is no longer available > on Linux, and we only use MariaDB on Windows, too. The DebugView log is > urgently needed here to see if we can fix anything. > > Maik Maik, MariaDB is available for Linux. Why do you say it isn't? I'm having problems setting up DigiKam with MariaDB/MySQL on Linux, but it works with MariaDB on Windows. I believe it was just a typo—what Maik likely meant is that MySQL isn't available on some specific Linux flavors, although it's generally available on most Linux distributions. However, MariaDB is increasingly being preferred over MySQL, and it's possible that in the future, MariaDB may completely replace MySQL. That’s likely why digiKam is proactively moving toward MariaDB. (In reply to Papadopoulos Anastasios from comment #8) > (In reply to Maik Qualmann from comment #5) > > We no longer test with MySQL, only MariaDB. MariaDB is no longer available > > on Linux, and we only use MariaDB on Windows, too. The DebugView log is > > urgently needed here to see if we can fix anything. > > > > Maik > > Maik, MariaDB is available for Linux. Why do you say it isn't? I'm having > problems setting up DigiKam with MariaDB/MySQL on Linux, but it works with > MariaDB on Windows. I believe it was just a typo—what Maik likely meant is that MySQL isn't available on some specific Linux flavors, although it's generally available on most Linux distributions. However, MariaDB is increasingly being preferred over MySQL, and it's possible that in the future, MariaDB may completely replace MySQL. That’s likely why digiKam is proactively moving toward MariaDB. Right, that was a typo. MySQL is no longer officially available as a distribution package, at least here on openSUSE Tumbleweed. It might still be available as a community package or directly from Oracle. Nevertheless, I would like to at least fix this bug and will install MySQL on my Windows test machine. Maik (In reply to Maik Qualmann from comment #11) > Right, that was a typo. MySQL is no longer officially available as a > distribution package, at least here on openSUSE Tumbleweed. It might still > be available as a community package or directly from Oracle. > > Nevertheless, I would like to at least fix this bug and will install MySQL > on my Windows test machine. > > Maik I installed MariaDB on Linux but, I can't connect to it from another Linux distro; I can connect to MariaDB from Windows, and some Linux distros, but not OpenSUSE. Unfortunately, I don't know how to debug it. Take a look at this : https://mariadb.com/docs/server/mariadb-quickstart-guides/mariadb-remote-connection-guide On openSUSE, the MySQL port (3306) is closed by default through the firewall. Use Yast to open the port. Maik (In reply to Maik Qualmann from comment #14) > On openSUSE, the MySQL port (3306) is closed by default through the > firewall. Use Yast to open the port. > > Maik Thanks Maik; my firewalld is disabled. I get the following when I try to test the connection: <<Database connection test was not successful. Error was: TLS/SSL error: SSL is required, but the server does not support it QMYSQL: Unable to connect>> (In reply to Papadopoulos Anastasios from comment #15) > (In reply to Maik Qualmann from comment #14) > > On openSUSE, the MySQL port (3306) is closed by default through the > > firewall. Use Yast to open the port. > > > > Maik > > Thanks Maik; my firewalld is disabled. I get the following when I try to > test the connection: > <<Database connection test was not successful. > Error was: TLS/SSL error: SSL is required, but the server does not support > it QMYSQL: Unable to connect>> I installed telnet on my system. telnet can attach to the port, but for some reason OSS DigiKam does not want to. OpenSUSE has enabled SSL for external MySQL connections in recent updates. You'll need to configure the appropriate SSL connection options in digiKam. Or disable SSL for external MySQL connections. Here is the bug report that it is intended: https://bugzilla.opensuse.org/show_bug.cgi?id=1242910 Maik Here is the bug report at digiKam: Bug 503894 Maik |