| Summary: | Crashes after not able to connect to database | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Wessel <wesselvanwyk> |
| Component: | Database-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | https://invent.kde.org/graphics/digikam/commit/f4c918d254a47c2dc7b15c3705ba8273d82bcf3e | Version Fixed In: | 7.3.0 |
| Sentry Crash Report: | |||
|
Description
Wessel
2021-04-05 15:09:31 UTC
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 |