[digikam] [Bug 435387] Crashes after not able to connect to database

2021-04-05 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=435387 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.3.0 Status|REPORTED

[digikam] [Bug 435387] Crashes after not able to connect to database

2021-04-05 Thread Wessel
https://bugs.kde.org/show_bug.cgi?id=435387 --- Comment #7 from Wessel --- 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. --

[digikam] [Bug 435387] Crashes after not able to connect to database

2021-04-05 Thread Wessel
https://bugs.kde.org/show_bug.cgi?id=435387 --- Comment #6 from Wessel --- (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 digika

[digikam] [Bug 435387] Crashes after not able to connect to database

2021-04-05 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=435387 --- Comment #5 from Maik Qualmann --- 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 wit

[digikam] [Bug 435387] Crashes after not able to connect to database

2021-04-05 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=435387 --- Comment #4 from Maik Qualmann --- You can also start a new configuration by renaming or deleting the "digikamrc": C:\Users\%USERNAME%\AppData\Local\digikamrc Maik -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 435387] Crashes after not able to connect to database

2021-04-05 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=435387 --- Comment #3 from Maik Qualmann --- 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

[digikam] [Bug 435387] Crashes after not able to connect to database

2021-04-05 Thread Wessel
https://bugs.kde.org/show_bug.cgi?id=435387 --- Comment #2 from Wessel --- (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 ins

[digikam] [Bug 435387] Crashes after not able to connect to database

2021-04-05 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=435387 --- Comment #1 from Maik Qualmann --- 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. M

[digikam] [Bug 435387] Crashes after not able to connect to database

2021-04-05 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=435387 Maik Qualmann changed: What|Removed |Added Severity|critical|crash CC|