| Summary: | Unconfirmed faces do not show up | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Stefan <StefanLinke> |
| Component: | Faces-Workflow | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | metzpinguin |
| Priority: | NOR | ||
| Version: | 7.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed In: | 7.9.0 | |
| Sentry Crash Report: | |||
| Attachments: | DigikamDebug Log | ||
|
Description
Stefan
2022-09-02 07:12:18 UTC
*** Bug 458628 has been marked as a duplicate of this bug. *** Please download DebugView from Microsoft and start it. Activate the internal debugging in the digiKam setup under Miscellaneous-> System and start digiKam again. Now play with the Unconfirmed face tag/view and post all the output from the DebugView window. Maik Created attachment 151781 [details]
DigikamDebug Log
Hi Mike, thanks for looking into this. I wasn't able to filter out the non-Digikam related lines, but I think the log does the job. Best regards Stefan The log doesn't show any problems at first, but I could only tell if the database was still consistent if I examined it. What strikes me, you have activated the database cleanup at the start? Since I've never been able to reproduce the specific issues with unconfirmed faces shown and not present in the view, the enabled database cleanup could be the trigger for the issues. Maik Hi Maik, I had "Maintenance" -> "Database Clean-Up" enabled and the "Settings" -> "Miscellaneous" -> "Search for new Items on Start-Up" (tranlated to the best of my knowledge) and disabled that now, but after I switched both items off, there is no change. Have I found the right settings? Best regards Stefan Yes, this is the option for cleaning up the database. I consider this option completely unnecessary when starting digiKam. Cleaning up database is completely sufficient once a year, or if many images are always deleted and added, maybe once a month. This can then also be started in the maintenance tool. The problem as it is currently implemented, that we start scanning for new items and cleaning up the database at the same time, so that problems arise are already logical. Either we run both jobs in cascade or remove clean up database completely from the startup. Maik Hi Maik, I did a full clean with all options manually and turned of the automatic maintenance at start-up, but the issue still persists. Best regards Stefan Your database is broken, we probably won't be able to fix it with an update. We can only prevent it from happening again if possible. You will have to start with a new database. How big is the digiKam.4.db if you create a ZIP file? Is it possible to send it to me and I can see if it can be fixed? Maik Git commit 6cdf371b949812ff5e68b5d9989c8332ed13c657 by Maik Qualmann. Committed on 02/09/2022 at 20:08. Pushed by mqualmann into branch 'master'. move clean up database to the splash screen stage and wait for ready Related: bug 432760 M +19 -6 core/app/main/digikamapp.cpp https://invent.kde.org/graphics/digikam/commit/6cdf371b949812ff5e68b5d9989c8332ed13c657 Git commit be99547043a370206dc6592cff2ac2174622c3f8 by Maik Qualmann. Committed on 02/09/2022 at 20:12. Pushed by mqualmann into branch 'qt5-maintenance'. move clean up database to the splash screen stage and wait for ready Related: bug 432760 M +19 -6 core/app/main/digikamapp.cpp https://invent.kde.org/graphics/digikam/commit/be99547043a370206dc6592cff2ac2174622c3f8 (In reply to Maik Qualmann from comment #9) > Your database is broken, we probably won't be able to fix it with an update. > We can only prevent it from happening again if possible. You will have to > start with a new database. How big is the digiKam.4.db if you create a ZIP > file? Is it possible to send it to me and I can see if it can be fixed? > > Maik Hi Maik, my database as zip file is 16.8 MB, I can send it to you, if that isn't too big. Best regards Stefan Yes, try it, GMail accepts attachments up to 25 MB. Maik The database actually does not contain any Unconfirmed face regions in the ImageTagProperties table. The fact that no images are displayed is correct according to the status of the database. The cause could have been the database cleanup at the digiKam start together with the search for new images. Create a new face recognition training database in the maintenance tool and restart face recognition to have Unconfirmed faces again. For the time being I'm closing the bug, if the problem occurs again with the corrected version, open this bug again. Maik |