https://bugs.kde.org/show_bug.cgi?id=429963
--- Comment #16 from vadeinpa...@gmail.com --- (In reply to Maik Qualmann from comment #15) > Now the "Settings" table does not seem to exist in the core database. You > should no longer work with this database either. I have no explanation. I > tested the internal MySQL a week ago under Windows without any problems, but > I will check it again in the next few days. > > Maik Aloha, Thanks for response. There may be significant differences between the way you test digikam with internal DB and they way I work with it over time. To illustrate, I did a clean install of digikam and MariaDB (removing all configuration and data files). After going through the initial digikam setup as part of the first launch (and specifying an album with thousands of images on my HDD), I close digikam. In Windows, the digikam process is still consuming CPU and Disk after the application shuts down. Now terminate the process. I do not know what happens internally, but the end result is rather similar to what I described in a previous comment. Similar situation may happen in other scenarios. For example, chose a large (say, 1000) unknown faces and assign them to a name. This takes some time. During that time, assign names to other unknown face (or even to faces in the first group) and terminate digikam. My gut feeling is that somewhere in the graceful failover there may be a glitch. All the Best; --Haim -- You are receiving this mail because: You are watching all bug changes.
