SUMMARY After showing UAC prompt, installer fails to launch on Windows 10 22H2 STEPS TO REPRODUCE 1. Download installer 2. Double-click installer .exe file 3. Click Yes on UAC prompt OBSERVED RESULT Nothing happens. EXPECTED RESULT Installation proceeds. SOFTWARE/OS VERSIONS Windows: 10 22H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
digiKam Windows installer is a non signed package. Check if you need to tune right somewhere in Windows Control Panel to execute the program. Typically, an Anti-Virus can block in background the install stage because it do not recognize the program as safe. Of course, it is... Here with my Windows 10 computer, there is no problem to install digiKam. Gilles Caulier
I'm aware it's an unsigned package; I've never had an issue installing it previously. This is the 1st build I've had problems with. I use Windows Defender and the protection log shows no corresponding entry. Same issue on a separate Windows 10 machine, also running 22H2 (19045.2486, to be precise) & Windows Defender. Even the in-app updater fails. FWIW the project should sign its installer. The fact that it's FLOSS is no excuse: OBS Studio is FLOSS and its installer is signed. In the same manner one would not expect Linux users to install binaries from an unsigned repo, Windows users should not be forced to run unsigned installers.
Signing installer introduce limitation and complexity. See the story here : https://bugs.kde.org/show_bug.cgi?id=398582 In others words, you must use Windows system to compile whole digiKam, and you lost the Mysql/MariaDb support, ... and more... Gilles Caulier
You can try the signed version compiled under Windows and MSVC here, just to try installer. but do not claim that you lost features compared to the non signed version cross compiled under Linux. https://binary-factory.kde.org/view/Windows%2064-bit/job/Digikam_Nightly_win64/ Gilles Caulier
(In reply to caulier.gilles from comment #3) > Signing installer introduce limitation and complexity. See the story here : > > https://bugs.kde.org/show_bug.cgi?id=398582 > > In others words, you must use Windows system to compile whole digiKam, and > you lost the Mysql/MariaDb support, ... and more... > > Gilles Caulier Ah, I see
(In reply to caulier.gilles from comment #4) > You can try the signed version compiled under Windows and MSVC here, just to > try installer. but do not claim that you lost features compared to the non > signed version cross compiled under Linux. > > https://binary-factory.kde.org/view/Windows%2064-bit/job/ > Digikam_Nightly_win64/ > > Gilles Caulier The installer launches just fine on that one, so it seems the signature really is the difference there. I think I'll wait for the next digiKam build to fix the issue since, as I said, I've never had this issue with digiKam previously.
(In reply to caulier.gilles from comment #4) > You can try the signed version compiled under Windows and MSVC here, just to > try installer. but do not claim that you lost features compared to the non > signed version cross compiled under Linux. > > https://binary-factory.kde.org/view/Windows%2064-bit/job/ > Digikam_Nightly_win64/ > > Gilles Caulier Update: The problem has persisted through the latest stable release, so I tried the signed Nighly Win64 build. It installed perfectly with no loss of the features I use. Thanks!