| Summary: | Problem with MYSQL-Backend | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | r.laue |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 5.7.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 5.8.0 | |
| Sentry Crash Report: | |||
For this problem with MariaDB >= 10.2 and QTBUG-63108 there is a workaround in the upcoming digiKam-5.8.0. Maik You can test with 5.8.0 pre release bundle available here : https://files.kde.org/digikam/ Gilles Caulier Note: If you use localhost as the server address in the settings, you have to change this for the AppImage in 127.0.0.1. Otherwise you can not connect to server with the AppImage. Maik |
Problem with internal and external mysql-backend Output: digikam.dbengine: Error while opening the database. Error details [ QSqlError("2059", "QMYSQL: Es kann keine Verbindung aufgebaut werden", "Plugin pvio_socket could not be loaded: not initialized") ] Internal and external backend were working until the update within 5.7.0. OS: SuSE Tumbleweed