Bug 517786 - Approving Faces, View Jumps to Another Photo Somewhere Else
Summary: Approving Faces, View Jumps to Another Photo Somewhere Else
Status: RESOLVED DUPLICATE of bug 402322
Alias: None
Product: digikam
Classification: Applications
Component: Faces-Workflow (other bugs)
Version First Reported In: 9.1.0
Platform: Microsoft Windows Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-03-18 19:09 UTC by Andy
Modified: 2026-03-19 19:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy 2026-03-18 19:09:18 UTC
Hi!

I'm back in the faces view and want to approve, reject, or delete faces.
While I'm clicking, the view keeps jumping to a different location and selecting a random photo.
Presumably, the face is somehow related to the photo I was just editing. Maybe a neighboring photo from the album or something. Then I scroll back to where I was and continue working. Until it happens again.
It might be related to the sorting of the entries. Currently, it's set to "Manual and by Date." But it's happened to varying degrees with other sorting options as well.
Or perhaps the neighboring face isn't always automatically selected after the approved photo disappears. It doesn't always jump to a different location.
It would be much better if the view always stayed where I was working.

I also noticed that when writing to the database or the metadata, everything jumps down one line and then back up. The photo being edited is briefly displayed at the very top in its own category (I think it's called "1 Face"). Because of this, I've occasionally clicked on and assigned the wrong face. Perhaps this behavior could be moved to the very bottom?

Best Regards
Andy
Comment 1 caulier.gilles 2026-03-19 02:14:11 UTC

*** This bug has been marked as a duplicate of bug 402322 ***
Comment 2 Andy 2026-03-19 19:13:10 UTC
Hmm, okay. I read about that case. But it's a bit different from mine. In my case, facial recognition is already complete and doesn't run automatically in the background.

But maybe it's more similar than I think. :)

Andy