SUMMARY After installation I try to run digiKam. It gives an error while opening the database, then try to reconnect until I click "Cancel. STEPS TO REPRODUCE 1. Do a fresh installation of Digikam (7.2.0) on Windows 10, after I downloaded the installation package. 2. Run DigiKam. It gives an "error while opening the database", and tries to reconnect until I click "Cancel". 3. It then responds with an error "Failed to open the database", saying that it will attempt to start, even tholugh it won't be functional. I click OK. 4. The splacreen opens up, but it crashes shortly afterwards, sending an error report to Microsoft. OBSERVED RESULT DigiKam does not open EXPECTED RESULT DigiKam should connect to db and open. SOFTWARE/OS VERSIONS Windows: 10 Home, build 19041.867 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The Readme after installation mentions "Internal database server require to install localy a database backend for Windows, as Mysql or MariaDB." I am not sure if this menas that the installation package would do it, or if the user need to do it manually?
If you start with digiKam, first select SQLite as the database backend. SQLite is nowhere near as much worse than MySQL to start with. Yes, MySQL requires an additional installation, e.g. from the MariaDB server. Maik
(In reply to Maik Qualmann from comment #1) > If you start with digiKam, first select SQLite as the database backend. > SQLite is nowhere near as much worse than MySQL to start with. Yes, MySQL > requires an additional installation, e.g. from the MariaDB server. > > Maik Thanks for the reply Maik. My current issue is that it crashes before I get an opportunity to set a database. Is there a config file that I can edit (set to the correct db) before I start digiKam?
Upload the DebugView Log so that we can see which configuration you are using, as described here for Windows: https://www.digikam.org/contribute/ Don't forget to set the debug environment variable. Maik
You can also start a new configuration by renaming or deleting the "digikamrc": C:\Users\%USERNAME%\AppData\Local\digikamrc Maik
I wonder how it is possible to create an invalid database configuration in the first setup? We test everything, path available, path writable, binary files available for MySQL, etc. The setup cannot be completed without a valid configuration. Maik
(In reply to Maik Qualmann from comment #4) > You can also start a new configuration by renaming or deleting the > "digikamrc": > > C:\Users\%USERNAME%\AppData\Local\digikamrc > > Maik I have deleted the existing digikamrc file, and digikam started successfully afterwards.. I had previously had a previous version of digikam installed, and thought I had removed all previous files - it could be possible that this file still remained. I have a backup of the file before I deleted it, if it would still help (or otherwise close this issue as "user error").
I makes sense now: my HD had crashed a few months ago, and the dcirectory structure (users) was slightly different after the rebuilt. The path under the database settings in the digikamrc file did not exist any more.
Git commit f4c918d254a47c2dc7b15c3705ba8273d82bcf3e by Maik Qualmann. Committed on 05/04/2021 at 19:20. Pushed by mqualmann into branch 'master'. show database settings dialog when database not found FIXED-IN: 7.3.0 M +51 -34 core/libs/album/manager/albummanager_database.cpp https://invent.kde.org/graphics/digikam/commit/f4c918d254a47c2dc7b15c3705ba8273d82bcf3e