Bug 511638 - No percentage update display
Summary: No percentage update display
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Faces-Recognition (other bugs)
Version First Reported In: 8.8.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-04 18:41 UTC by Thomas
Modified: 2025-12-19 04:02 UTC (History)
2 users (show)

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


Attachments
The start Log (122.31 KB, text/plain)
2025-11-11 05:01 UTC, Thomas
Details
Second Digicam Log (100.69 KB, text/plain)
2025-11-11 05:13 UTC, Thomas
Details
After delete the Picture (42.88 KB, text/plain)
2025-11-11 18:57 UTC, Thomas
Details
After delete the recognition.db (124.90 KB, text/plain)
2025-11-11 18:59 UTC, Thomas
Details
Still 0 or 100% (5.87 KB, image/png)
2025-11-14 04:26 UTC, Thomas
Details
Crash afer the start (110.00 KB, text/plain)
2025-12-07 16:16 UTC, Thomas
Details
Studio (86.24 KB, image/png)
2025-12-14 11:17 UTC, Thomas
Details
No Path (6.97 KB, image/png)
2025-12-16 18:49 UTC, Thomas
Details
unconfirmed Picture (92.78 KB, image/png)
2025-12-18 04:37 UTC, Thomas
Details
preview images (24.93 KB, image/png)
2025-12-18 04:40 UTC, Thomas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas 2025-11-04 18:41:34 UTC
Since version 8.8.0, I no longer see any percentage values, neither when updating the database, nor when reorganizing faces, nor when confirming faces, etc. It always says 0%. Everything worked fine with 8.7.0.
I use Digicam on Windows Server 2019 64.

Is there a log I should post about this?
Comment 1 Maik Qualmann 2025-11-04 19:55:08 UTC
We are now only updating the progress every 50 ms to prevent the GUI from slowing down. There are no problems here; I will test it on Windows tomorrow.
Do the 0% remain visible or do they disappear again?

Maik
Comment 2 Maik Qualmann 2025-11-04 21:03:21 UTC
Git commit f94a60bf26a15ad46522f5467c92582f28384bbe by Maik Qualmann.
Committed on 04/11/2025 at 21:02.
Pushed by mqualmann into branch 'master'.

use QTimer instead of QElapsedTimer
There are indications that QElapsedTimer does
not work correctly in threads and under Windows.

M  +4    -6    core/utilities/maintenance/manager/maintenancetool.cpp

https://invent.kde.org/graphics/digikam/-/commit/f94a60bf26a15ad46522f5467c92582f28384bbe
Comment 3 Maik Qualmann 2025-11-05 11:57:59 UTC
A digiKam pre-release with the latest change is available. Please test whether the problem is resolved and report back:

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

Maik
Comment 4 Thomas 2025-11-10 05:39:36 UTC
Hi, with version 8.9.0, digiKam doesn’t start on Windows Server 2019
Comment 5 caulier.gilles 2025-11-10 06:23:57 UTC
Do you seen an error on screen ? 

Can you take a look to this contribute page section for more investiguation:

https://www.digikam.org/contribute/#windows-host
Comment 6 Thomas 2025-11-11 05:01:37 UTC
Created attachment 186690 [details]
The start Log

No, there is no Error Screen, it comes the Start Screen and then nothing more. After a reboot of the System i see a small time the Gui and dann nothing, attached the  Log
Comment 7 Thomas 2025-11-11 05:13:07 UTC
Created attachment 186691 [details]
Second Digicam Log

I renamed the File who was last output in the first log and start Digicam new, now the Output of the Log is a outher, but the Problem is the same
Comment 8 Maik Qualmann 2025-11-11 07:10:30 UTC
This image appears to be causing a crash in the JPG Loader:

"D:/Bilder/Laya/2023/05-06_2023/Mai-Juni_2023 (53).jpg"

Please remove the image. If this is the cause, we would like to have it to help us determine the problem.

Additionally, the face recognition database "D:/Images/recognition.db" is corrupted. Please delete it; it will be recreated.

Maik
Comment 9 Thomas 2025-11-11 18:57:28 UTC
Created attachment 186709 [details]
After delete the Picture

Hi, thank you for your fast help, i think the problem is not the Image , i have delete it in the folder but the problem is the same
Comment 10 Thomas 2025-11-11 18:59:15 UTC
Created attachment 186710 [details]
After delete the recognition.db

Here the Log after the delete of recognition.db, the Problem is the same
Comment 11 Thomas 2025-11-11 19:14:45 UTC
I try it once again and now the lastr rows of the Log shows this

[8564] digikam.database: Attempt to create invalid tag pair image id 29235 tag id 0
[8564] kf.windowsystem: Could not find any platform plugin
[8564] digikam.metaengine: Check ExifTool availability: true
Comment 12 Thomas 2025-11-12 03:44:34 UTC
I tested it again and it seems to be a problem with QT6. Version 8.8.0 QT 6 gives the same log message and crashes, but version 8.8.0 QT 5 runs fine, except for the percentage display.
Comment 13 Maik Qualmann 2025-11-12 08:33:27 UTC
Okay, I also have a Windows 10 machine here (Server 2019 is also based on Windows 10) where the Qt6 version crashes. The cause is QWebEngine, which is causing a crash in a Windows DLL file. We'll see if it gets fixed in a newer Qt6 version in the future. A current Qt5 version for testing progress is available here:

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

Maik
Comment 14 Thomas 2025-11-14 04:26:01 UTC
Created attachment 186763 [details]
Still 0 or 100%

With QT5 8.9.0, Digicam does not crash, but the percentage remains at 0 or 100%. The process has been running for about 10 hours now and is still at 0.
Comment 15 Maik Qualmann 2025-11-14 07:26:51 UTC
Git commit 72efe17621208d64f7cc15de3389dfbbf7fce630 by Maik Qualmann.
Committed on 14/11/2025 at 07:26.
Pushed by mqualmann into branch 'master'.

use check progress even for skipped images

M  +8    -1    core/utilities/maintenance/tools/facesmanagement/facesengine.cpp

https://invent.kde.org/graphics/digikam/-/commit/72efe17621208d64f7cc15de3389dfbbf7fce630
Comment 16 Maik Qualmann 2025-11-14 07:40:10 UTC
The fact that the process isn't terminating must have another cause.
I see these messages in the log; we've seen this before:

Attempt to create invalid tag pair image id 29235 tag id 0

It's processing a "empty" face; we need to investigate.

Maik
Comment 17 Maik Qualmann 2025-11-19 20:18:50 UTC
Git commit 6420b11bf7507db2ddc33d983f531d8483e4c618 by Maik Qualmann.
Committed on 19/11/2025 at 20:18.
Pushed by mqualmann into branch 'master'.

prevent double activation event when using the Return key

M  +11   -2    core/libs/tags/widgets/addtagslineedit.cpp

https://invent.kde.org/graphics/digikam/-/commit/6420b11bf7507db2ddc33d983f531d8483e4c618
Comment 18 caulier.gilles 2025-12-07 11:43:43 UTC
Thomas,

Can you check the last Maik fixes included in digiKam 8.9.0 pre-release available here : 

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

Gilles Caulier
Comment 19 Thomas 2025-12-07 16:16:16 UTC
Created attachment 187417 [details]
Crash afer the start

Hello,
with the latest x64 QT6 DigiCam starts but Crashes then directly, Attached the Log
Comment 20 caulier.gilles 2025-12-07 16:42:20 UTC
There is nothing special to see in the debugview trace. All sounds like normal for me.

We need the Microsoft debugger trace. It's explained here :

https://www.digikam.org/contribute/#windows-host-1

Best regards

Gilles Caulier
Comment 21 Thomas 2025-12-14 11:17:56 UTC
Created attachment 187627 [details]
Studio

I'm not familiar with Studio and the QT debugger, so I'm not sure if this is what you need.
Comment 22 Maik Qualmann 2025-12-14 11:47:25 UTC
I also experienced this crash on one of my Windows test systems. The crash originates from the QWebEngine component and ends with the usrtbase.dll file. Gilles plans to rebuild digiKam for Windows (newer Qt version etc) over Christmas.

In my case, the cause was the old Intel HD graphics driver; there isn't a newer driver available. I switched to the Microsoft Basic graphics driver, and there are no limitations. digiKam no longer crashes on this machine.

Maik
Comment 23 Thomas 2025-12-14 13:02:07 UTC
Hi, this is a nice workaround, t tryed it also, and at this time it seems to be run fine at the moment
Comment 24 Thomas 2025-12-16 18:49:55 UTC
Created attachment 187708 [details]
No Path

Hi, I don't know if this is related, but in the “Properties” window, the path is no longer displayed, only the drive. This was different before, as the complete path was always shown.
Comment 25 caulier.gilles 2025-12-16 20:16:06 UTC
The path problem is just a display problem. It's fixed in next 8.9.0
Comment 26 Thomas 2025-12-18 04:37:46 UTC
Created attachment 187766 [details]
unconfirmed Picture

Hello, thank you, I will wait for the next version. However, I still have a couple of things that are “strange.” I will just use this thread for that. If that is incorrect, please let me know. I have an image that always remains in the unconfirmed folder, no matter what I do with it, reject, accept, etc., it always stays there. What could be the reason for this?
Comment 27 Thomas 2025-12-18 04:40:49 UTC
Created attachment 187767 [details]
preview images

Sometimes I have preview images that are displayed repeatedly, but I can't see them in the preview because I get the message “Image cannot be loaded.” When I select “Open data management,” I am shown a completely different folder where the image is not located.
Comment 28 Thomas 2025-12-18 04:42:16 UTC
And then there is the case where thumbnails are displayed, but when I want to view them in the preview, I get the message “Image cannot be loaded.” I cannot view these in the file manager either.  What can I do?  Thank you ver
Comment 29 caulier.gilles 2025-12-18 05:44:08 UTC
please shre the problematic image for investigation
Comment 30 Thomas 2025-12-19 04:02:32 UTC
I can't Upload the Image here "The file you are trying to attach is 5952 kilobytes (KB) in size. Attachments cannot be more than 4000 KB.
We recommend that you store your attachment elsewhere and then paste the URL to this file on the attachment creation page in the appropriate text field, which you can access by clicking the "paste text as attachment" link.
Alternately, if your attachment is an image, you could convert it to a compressible format like JPG or PNG and try again."