Bug 286452

Summary: No way to scan untagged photos for faces, or scan ALL folders
Product: [Applications] digikam Reporter: Zack Evans <zack23evans>
Component: Faces-WorkflowAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: minor CC: caulier.gilles
Priority: NOR    
Version: 2.3.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 7.0.0
Sentry Crash Report:

Description Zack Evans 2011-11-12 22:57:48 UTC
Version:           2.3.0 (using KDE 4.7.3) 
OS:                Linux

You have to select one or more folders AND tags in the "scan collection for faces" dialog. There is no way to select "all photos in the folder" or "untagged". So, if you haven't tagged your photo with anything there's no way to ask digikam to scan it.

Reproducible: Always

Steps to Reproduce:
See details.

Actual Results:  
No photos are scanned.

Expected Results:  
All photos in the album selected should be scanned if you have not chosen any tags to scan.
Comment 1 Marcel Wiesweg 2011-11-13 15:41:46 UTC
There is no conjunction between the chosen albums or tags. The implementation is the simplest possible: All checked albums or tags are put in a list and scanned one after the other. If you check no album and no tag, all albums will be scanned. Really, it's four lines of code.
There must be some other reason; maybe the photos are flagged as already scanned?
Comment 2 Zack Evans 2011-11-13 18:43:48 UTC
Well, I figured the code must be like that, I was bit surprised by this bug too. There is a different underlying cause I think. 

Now I have tested that the face scanning itself is working by tagging everything in an album with the same tag, selected that album AND that tag, and letting it scan. That worked.

Now guess what - if I unselect everything so it's back to Any Album / Any Tag - it's now scanning away, in all the other albums, no problem. So it seems to be an issue with first use?

I won't be able to reproduce that without building another Linux install however... if someone has a test machine around can they just try this theory?

It wasn't an issue with them already being scanned because the rescan option also had the same problem.
Comment 3 Marcel Wiesweg 2012-02-20 20:49:55 UTC
Any more insight here?
Comment 4 caulier.gilles 2014-08-24 09:15:43 UTC
For me i cannot reproduce the dysfunction described here using last digiKam 4.2.0.

Please give us a fresh feedback using last stable release.

Or perhaps i don't understand the obscur explanations given here... 

Gilles Vaulier
Comment 5 caulier.gilles 2015-06-28 09:40:21 UTC
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier
Comment 6 caulier.gilles 2015-08-22 06:40:07 UTC
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.
Comment 7 caulier.gilles 2016-07-14 06:03:00 UTC
This file still valid using last stable 5.0.0 release ?
Gilles Caulier
Comment 8 caulier.gilles 2017-04-16 20:10:26 UTC
digiKam 5.5.0 is released officially

https://download.kde.org/stable/digikam/

...and new 5.6.0 pre-release as bundle is available here :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Please check if this problem still reproducible with these versions.

Thanks in advance

Gilles Caulier
Comment 9 caulier.gilles 2017-06-22 21:39:07 UTC
digiKam 5.6.0 is now release and available as bundle for Linux, MacOS and Windows.

Can you check if problem still exists with this version ?

Thanks in advance

Gilles Caulier
Comment 10 caulier.gilles 2017-11-30 09:31:24 UTC
Please update this entry from bugzilla with current 5.8.0 pre-release bundle to see if problem remain.

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier
Comment 11 caulier.gilles 2019-12-23 15:34:16 UTC
7.0.0-beta1 is out with new Face Recognition algorithm based on Deep
Learning/Neural Network API from OpenCV

https://download.kde.org/unstable/digikam/

Please test and give us a feedback

Thanks in advance
Gilles Caulier
Comment 12 caulier.gilles 2019-12-25 17:54:29 UTC
Following the comments #1 and #2 there is no more to do in this file. I close it now.

Gilles Caulier