Bug 483995 - Failure to download required files for face detection, red-eye removal and auto-tagging of images
Summary: Failure to download required files for face detection, red-eye removal and au...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Setup-FirstRun (show other bugs)
Version: 8.3.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-19 12:54 UTC by Alan Howshall
Modified: 2024-03-28 07:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 8.4.0


Attachments
First received download error (2.53 MB, image/png)
2024-03-19 12:54 UTC, Alan Howshall
Details
Second received download error (2.52 MB, image/png)
2024-03-19 12:54 UTC, Alan Howshall
Details
Third attempt from alternate location successfully downloading progress (2.52 MB, image/png)
2024-03-19 12:55 UTC, Alan Howshall
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Howshall 2024-03-19 12:54:06 UTC
Created attachment 167467 [details]
First received download error

SUMMARY
On fresh install of 8.3.0 64bit on Windows 10 during first run of DigiKam, when prompted to install additional binaries to allow facial, red-eye and auto-tagging of images I received errors the first two times that DigiKam attempted to download yolov5x_batch_16_s320.onnx part of download.

The first time I got an error it was with a 'Connection closed' message (see 1st screenshot) 

On selecting 'Try again' the download re-attempted, but I received a different more detailed error page that confirmed an 'Error transferring' problem with and same file (see 2nd screenshot). 
Attempting to be retrieved from https://mirror.faigner.de/kde/files/digikam/autotags/yolov5x_batch_16_s320.onnx - Which does not appear to be a valid location.

On selecting 'Try again' again the same yolov5x_batch_16_s320.onnx did progress successfully, but from a different mirror (see 3rd screenshot)

STEPS TO REPRODUCE
1. Download /digikam/8.3.0/digiKam-8.3.0-Win64.exe (I downloaded mine from https://mirrors.ukfast.co.uk/sites/kde.org/ftp/stable/digikam/8.3.0/digiKam-8.3.0-Win64.exe)
2. Install as a complete fresh install
3. When prompted say yes to installing additional face and image tagging binaries
4. Some configured mirror locations do not contain additional files

OBSERVED RESULT
Received multiple errors trying to download prompted additional binary files

EXPECTED RESULT
That downloads should have worked from first location

SOFTWARE/OS VERSIONS
Windows: Edition	Windows 10 Pro
Version	22H2
Installed on	‎04/‎01/‎2023
OS build	19045.4170
Experience	Windows Feature Experience Pack 1000.19054.1000.0

macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Alan Howshall 2024-03-19 12:54:45 UTC
Created attachment 167469 [details]
Second received download error
Comment 2 Alan Howshall 2024-03-19 12:55:50 UTC
Created attachment 167470 [details]
Third attempt from alternate location successfully downloading progress
Comment 3 Maik Qualmann 2024-03-19 14:21:07 UTC
If I understand correctly, they were able to complete the download after the 3rd attempt. The behavior is normal, we do not have control over the KDE project's globally distributed mirror servers, some of which are at universities, for example. Not everyone is always online either. If the primary address that automatically selects a server near your country fails, we try "good" known mirror servers directly. We introduced this behavior following bug reports.

Maik
Comment 4 Alan Howshall 2024-03-19 20:47:08 UTC
You are correct that the download did work for me on the third attempt. However as a UX designer I would suggest most users would likely only 'Try again' a failed download 1x, before choosing 'Cancel' button that would lead to less optimal results UNLESS you explicitly tell the user that you will automatically re-try from a different download location.

So it's great that you've implemented that alternate download location functionality (as I understand what you're saying about not having direct control over mirror sources) BUT I would recommend either adding some additional text to those error dialogs saying that you will re-try from a different mirror. Maybe along with re-labelling current generic and repeated 'Try again' button wording with something like 'Try alternate'.

So the user understands that there's a decent chance of it working if they click the Try button more than once. Which was not something I expected. I only tried 3 times because had the same error during 8.2.0, put after cancel that had left me with a crashing 8.2.0 whenever any tagging was involved. Hence I was looking to gather extra evidence of a problem with these additional downloads on fresh 8.3.0 install.

Thanks in advance, Alan
Comment 5 Maik Qualmann 2024-03-19 22:00:49 UTC
Git commit 40333f00b017b7bc206819b318ab503b4b2bc2c5 by Maik Qualmann.
Committed on 19/03/2024 at 22:00.
Pushed by mqualmann into branch 'master'.

adjust dialog text if an error occurs during download
FIXED-IN: 8.4.0

M  +1    -1    NEWS
M  +4    -3    core/utilities/setup/downloader/filesdownloader.cpp

https://invent.kde.org/graphics/digikam/-/commit/40333f00b017b7bc206819b318ab503b4b2bc2c5
Comment 6 Maik Qualmann 2024-03-28 07:31:49 UTC
Git commit 5f59408034214605a359ad35d13ee966ac9dac25 by Maik Qualmann.
Committed on 28/03/2024 at 07:30.
Pushed by mqualmann into branch 'master'.

remove fixed alternative download server,
at the request of the KDE Sysadmin.
The Geo IP databases for the mirror
servers used have been updated.
Related: bug 449815

M  +9    -26   core/utilities/setup/downloader/filesdownloader.cpp [INFRASTRUCTURE]

https://invent.kde.org/graphics/digikam/-/commit/5f59408034214605a359ad35d13ee966ac9dac25