Bug 499301 - Facial recognition database update not working
Summary: Facial recognition database update not working
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Faces-Engine (show other bugs)
Version: 8.6.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-30 06:19 UTC by Roland
Modified: 2025-02-01 03:56 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 8.6.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roland 2025-01-30 06:19:01 UTC
SUMMARY
With the newest dev release, if the digikam instance has a facial recognition database a prompt is presented on startup. This prompt says the database (format) is out of date etc and needs to be updated. A click on OK is supposed to have this process run in the background. The app closes, and no process seems to spawn/no CPU resources are being used, and the app doesnt restart. Manually restarting digikam yields this database prompt again...

STEPS TO REPRODUCE
1. Start digikam where the instance has a facial recognition database active
2.  Click OK to the prompt requesting approval for this process to happen


OBSERVED RESULT
App closes, and I see no evidence of any spawned process or any CPU/RAM allocation to any unknown process. App does not open on its own, and a manual restart repeats this cycle...

EXPECTED RESULT
Presumably, the app is supposed to open, while the database updates in the background (per the prompt dialog)

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 caulier.gilles 2025-01-30 07:11:01 UTC
Hi,

The Windows build published yesterday evening are not complete. Some more commit was done later and new build will be avaialble this morning. Please try again when it ready:

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

Best

Gilles Caulier
Comment 2 caulier.gilles 2025-01-30 07:28:16 UTC
Git commit 5a6dac20c0f6924ff7e39e1ee06b41bfbb878733 by Gilles Caulier.
Committed on 30/01/2025 at 07:27.
Pushed by cgilles into branch 'master'.

allocate dialog with new operator and protect with QPointer
Related: bug 499305

M  +8    -6    core/app/main/digikamapp_tools.cpp
M  +1    -1    core/utilities/facemanagement/dialogs/facetrainingupgradedlg.cpp

https://invent.kde.org/graphics/digikam/-/commit/5a6dac20c0f6924ff7e39e1ee06b41bfbb878733
Comment 3 caulier.gilles 2025-01-30 13:54:37 UTC
Git commit ff6753122cbb910158fe1307e38425e747fa04f0 by Gilles Caulier.
Committed on 30/01/2025 at 13:53.
Pushed by cgilles into branch 'master'.

assert if model is not YuNet.
Related: bug 499305

M  +0    -12   core/libs/facesengine/detection/opencv-dnn/opencvdnnfacedetector.cpp

https://invent.kde.org/graphics/digikam/-/commit/ff6753122cbb910158fe1307e38425e747fa04f0
Comment 4 Roland 2025-01-31 05:57:57 UTC
Hi-

Im not sure if there was a fix on this published or not. I say this because I have 2 instances of digiKam, and with the update in place, one instance completes the face recognition rebuild process correctly- where the GUI opens and the task state/progress bar behave as expected. The other instance behaves as if the bug remains. The core difference between the 2 instances is that the later has far more content (sort of 100,000 images), where the former has more like 5,000. 

Im using the method your team mentioned for multiple instances on a single PC- where I have a -config xxx argument in the shortcut(s) which point to different config files. Point here is that the core application files are physically the same except for the databases, and the file counts. 

Best
Comment 5 caulier.gilles 2025-01-31 06:28:59 UTC
yes, please we fix some dysfunctions yesterday. Please try with the new 8.6.0 pre release Windows installer.

Thanks in advance

Gilles Caulier
Comment 6 Michael Miller 2025-01-31 19:05:24 UTC
(In reply to Roland from comment #4)
> Hi-
> 
> Im not sure if there was a fix on this published or not. I say this because
> I have 2 instances of digiKam, and with the update in place, one instance
> completes the face recognition rebuild process correctly- where the GUI
> opens and the task state/progress bar behave as expected. The other instance
> behaves as if the bug remains. The core difference between the 2 instances
> is that the later has far more content (sort of 100,000 images), where the
> former has more like 5,000. 
> 
> Im using the method your team mentioned for multiple instances on a single
> PC- where I have a -config xxx argument in the shortcut(s) which point to
> different config files. Point here is that the core application files are
> physically the same except for the databases, and the file counts. 
> 
> Best

Hi Roland,
Can you verify the issue is resolved in the most recent daily build?

Cheers,
Mike
Comment 7 Roland 2025-01-31 21:51:28 UTC
Yes, it seems to be resolved. On opening my instance with the larger collection, the facial database update prompt was triggered, the GUI opened, and the background process started.

Thanks for getting this fixed so quickly-

Roland