| Summary: | Could not start database initializer | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | dajomu <dajomu1> |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | grave | CC: | ayr035, caulier.gilles, KDE, metzpinguin, rebollo.h |
| Priority: | NOR | ||
| Version: | 6.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.0.0 | |
| Sentry Crash Report: | |||
|
Description
dajomu
2017-05-17 21:35:10 UTC
digiKam 5.6.0 is now released and available as bundle for Linux, MacOS and Windows. https://www.digikam.org/news/2017-06-21-5.6.0-release-announcement/ Can you check if problem still exists with this version ? Thanks in advance Gilles Caulier A similar problem occurs in version 5.6. Digikam can not connect to the existing database. In order to use the program I had to create a new user and configure from scratch digikam. So far I've lost 4 years of work. (Labels, albumens, people, etc. I've lost everything !!) *** En la versión 5.6 sucede un problema similar. Digikam no puede conectarse con la base de datos existente. Para poder utilizar el programa tuve que crear un nuevo usuario y configurar desde cero digikam. Hasta ahora he perdido 4 años de trabajo. (etiquetas, albumens, personas, etc. lo he perdido todo!!) ** New digiKam 5.7.0 are built with current implementation as pre-release bundles: https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Problem still reproducible ? Do you use MAriaDB or Mysql server ? Which version exactly ? Gilles Caulier With next 5.8.0 release Mysql support have been well improved and a lots of bugs fixed. Please test with pre release 5.8.0 bundles that we provide and give us a feedback https://files.kde.org/digikam/ Thanks in advance Gilles Caulier The two projects MySQL and MariaDB continue to drift apart. It is becoming increasingly difficult to support both databases. Also, we would have to consider different versions of a database in the future. Maybe MariaDB will replace the program "mysql_install_db" at some point. But I think that in the future we can only support one database. That will probably be MariaDB. Maik I also seen this branching state between these project. I vote also for Mariadb, which remplace Mysql everywhere de facto under Linux World. Gilles Caulier Can you reproduce the dysfunction using digiKam 6.0.0 pre-release bundle available here : https://files.kde.org/digikam/ I can confirm this bug affected digiKam 5.9.0 and 6.0.0 beta 2, both on KDE Neon (bionic) and MySQL server 5.7.24. Besides the issue mentioned in #c0 (mysql_install_db is deprecated), there's another issue caused by wrong parameters order. In according to MySQL docs [1] the argument --defaults-file must be the first. More info about the initializing in MySQL 5.7 on [2] The initialization command that worked for me was `mysqld --defaults-file=/home/mik/.local/share/digikam/mysql.conf --initialize --datadir=/home/mik/.local/share/digikam/db_data --server-id=1` [1] https://dev.mysql.com/doc/refman/5.7/en/option-file-options.html [2] https://mysqlserverteam.com/initialize-your-mysql-5-7-instances-with-ease/ Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just released ? https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/ I can confirm this issue still exists in digikam 6.4.0 (on archlinux). My understanding is that the --defaults-file argument must come before any other option on the commandline in both mysql and mariadb. Works fine with MariaDB here, but of course we can change it. Maik Git commit 6d386540102043d2c70c98e5b20f24cde6531343 by Maik Qualmann. Committed on 31/12/2019 at 19:32. Pushed by mqualmann into branch 'master'. change order from the "--defaults-file" option M +2 -1 core/libs/database/server/databaseserver.cpp https://invent.kde.org/kde/digikam/commit/6d386540102043d2c70c98e5b20f24cde6531343 |