https://bugs.kde.org/show_bug.cgi?id=441092

            Bug ID: 441092
           Summary: Ability to resume "clear and rebuild all training
                    data"
           Product: digikam
           Version: 7.3.0
          Platform: Mint (Ubuntu based)
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Faces-Maintenance
          Assignee: digikam-bugs-n...@kde.org
          Reporter: jan...@inbox.lv
  Target Milestone: ---

SUMMARY

For a sufficiently large photo collection, "Clear and rebuild all training
data" for face recognition takes a lot of time. If digiKam is restarted during
the process, the process seems to be stopped (incomplete?, cancelled? undone?)
without any messages and explanations, and does not resume in order to get
properly finished.

STEPS TO REPRODUCE

1. Have a large collection of images with marked faces.
2. Tools -> Maintenance -> Clear and rebuild all training data
3. Let it run to 10%.
4. Close digiKam.
5. Open digiKam.

OBSERVED RESULT

When closing, no warning about interrupting face rebuilding process and
information about consequences.
When digiKam is reopened, nothing happens, no maintenance process is resumed.

EXPECTED RESULT

When digiKam is reopened, the face DB rebuilding process should be resumed.

If not, at least a warning about interrupting face rebuilding process and
information about consequences should be displayed when closing digiKam.

In my opinion, an even better UX approach would be if the rebuilding process
could be done in the background, on demand – as soon as any face-related data
gets changes (e.g., the user confirms a new face), so the user does not have to
worry about existence of such maintenance commands, and when or whether they
should be executed.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Mint 20.1
KDE Plasma Version: 
KDE Frameworks 5.68.0
Qt 5.12.8 (built against 5.12.8)

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to