Bug 489625 - Most recent weekly doesnt start under windows (ucrtbase.dll error)
Summary: Most recent weekly doesnt start under windows (ucrtbase.dll error)
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Bundle-Windows (show other bugs)
Version: 8.4.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-02 16:07 UTC by Roland
Modified: 2024-10-14 04:16 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roland 2024-07-02 16:07:27 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
With the newest weekly release (dated 7.2.24), the install (at least, the update via the earlier installed version) will not start under Windows 10. There is no indication of the start process, and no error message displayed. 

In the Windows Logs/Application summary, the fault is summarized as an Application Error, in faulting module ucrtbase.dll v 10.0.19041.3636, exception code 0xc0000409 in the application path (\digikam\digikam.exe. Faulting module path is in windows\system32\

This is repeatable, where installing 8.3 over the newest weekly starts as usual, and updating within the app yields the same no start + Application Error entry.

I believe the dll is closely related to the VC++ redistributable package

STEPS TO REPRODUCE
1. Update running app to that released 7.2.24
2. Start the app via a shortcut
3. 

OBSERVED RESULT
No visual start. App error entry created in Application log for Windows

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 caulier.gilles 2024-07-02 16:09:05 UTC
Qt5 or Qt6 installer ?
Comment 2 Roland 2024-07-02 16:16:17 UTC
No idea. This is via the Online version checker built into the app, and I assume the installer is part of the app install. Since I had to revert to 8.3, and the About for that suggests QT version 6.6.1, Im assuming this and later variants on Win10 use QT6. If there is something specific I can check to clarify, please advise-
Comment 3 caulier.gilles 2024-07-02 16:45:05 UTC
Please, double check with the Windows installer Qt6 available here :

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

digiKam-8.4.0-20240702T152931-Qt6-Win64.exe

Gilles Caulier
Comment 4 Roland 2024-07-02 17:01:12 UTC
That variant seems to work correctly. Is the updater within the application defaulting to the QT5 variant? With the QT6 version of 8.3, the 'Help/Check for New Versions' seems to pull in a variant which doesnt start (presumably, the QT5 variant). I can check later- it seems show show the variant as QT5/QT6 under details for some of the files being installed during the actual update. I dont know if the updater is keeping the installer binary locally (i.e. in the web downloads directory), or if the binary is deleted as part of the updater process (i.e. spawns a thread to delete the installer once completed).

Best
R
Comment 5 Maik Qualmann 2024-07-02 19:27:20 UTC
Here the Qt5 version works on 2 different computers. On my laptop, however, the Qt5 version only starts with an empty (white) program window. Only after manually activating the software OpenGL option in the system config file does the Qt5 version start with a normal window.
However, the differences in the video player are significant; QtMultimedia in the Qt6 version plays audio files correctly and videos without stuttering.

Gilles, I would suggest that we generally save the Qt5 versions in a "legacy" folder to avoid confusion.

Maik
Comment 6 caulier.gilles 2024-07-02 20:03:11 UTC
Right i will push back the Windows Qt5 version in legacy as previously, including the AppImage version.

Gilles
Comment 7 Roland 2024-07-02 21:18:06 UTC
Much appreciated everyone. At least with my machine, the only indication I had of the error was hidden in the App error log for the System- there were no dialog boxes, no white screen, no 'not responding' process in the list etc. So, it could be very confusing for people who arent familiar with the lower level OS logging.

Best-
R
Comment 8 caulier.gilles 2024-07-03 07:52:29 UTC
Git commit 6cca2dec59bb2c496fc27bc7099cf70aaefce5ec by Gilles Caulier.
Committed on 03/07/2024 at 07:51.
Pushed by cgilles into branch 'master'.

use legacy subdir for the qt5 version of AppImage and Windows bundles

M  +4    -1    project/bundles/appimage/config.sh
M  +4    -1    project/bundles/vcpkg/config.sh

https://invent.kde.org/graphics/digikam/-/commit/6cca2dec59bb2c496fc27bc7099cf70aaefce5ec
Comment 9 caulier.gilles 2024-10-14 04:16:24 UTC
Git commit 3b27140943be99acb5adda18ca8448c4141df752 by Gilles Caulier.
Committed on 14/10/2024 at 04:12.
Pushed by cgilles into branch 'master'.

fix downloading file name templates
CCBUGS: 490378
CCBUGS: 490377

M  +11   -13   core/libs/onlineversion/onlineversionchecker.cpp
M  +5    -1    core/libs/onlineversion/onlineversiondlg.cpp
M  +5    -0    core/libs/onlineversion/onlineversiondwnl.cpp