I ran face recognition on my collection, and am editing the face tags. In a group picture with multiple faces, if I change one, i.e. add a name to an "unknown", or change the name of a mis-recognized, or add a new rectangle and name; after clicking "Ok", all the tags on the preview disappear. Moving off, then back on restores the tags (as does toggling "show face tags"). This makes it inconvenient to make multiple changes on one preview. Reproducible: Always Steps to Reproduce: 1. Open a photo with multiple faces and tags, but which require multiple additions/changes. 2. Add or change one of the tags 3. All the tags disappear from the preview. 4. Move off then back on the preview, or toggle off then on the "Show face tags", and they reappear. Actual Results: The tags disappear from the preview. Expected Results: All tags should remain showing to ease making multiple corrections.
when you said that "The tags disappear from the preview.", you want mean the FACE tags ? Gilles Caulier
Same bug still present in 4.2.0. On a photo with several face tags, open the view that shows one photo in large. Click the "show face tags" button to show all the face tags. Then change the name on one tag (assigning the face to a tag). Expected result: The face tag now shows the new name, and all the other face tags are unchanged. Actual result: All the face tags disappear from the view. Moving to another picture and moving back, or toggling the "show face tags" button, they appear again. I'm not sure if this may be related to whether tags are stored in the actual photo files, because every time I change tags on anything, the photo thumbnail briefly disappears when the tags are saved to the file.
Update: It does not happen every time. Sometimes it's possible to confirm one face tag (without changing the name) and the other tags remain.
*** Bug 326035 has been marked as a duplicate of this bug. ***
I also have this problem, and I got this bug with 4.1.0 and since I use Digikam (3.x). It happens evry time. Using Kubuntu 14.04 64bits
*** This bug has been marked as a duplicate of bug 334244 ***
Not reproducible using 7.0.0-beta1