Created attachment 114537 [details] Windows Event Log digiKam-6.0.0-beta1-20180819T150542-Win64. kbuildsycoca5.exe errors. Windows event logs attached.
I just rebuild the windows installer and fixed some points : 1/ now we have DrMinGW in background as crash handler. If the application has a dysfunction, Windows must propose to get a debug trace. DrMingw will be able to list the internal code trace from source code (as under Linux). This will help to investigate. 2/ I discovered a dysfunction in Lensfun 0.3.95 used previously. This lib in alpha stage has a bug under Windows which crash DK at init. I reverted the lib to a stable release, and crash disappear. https://www.flickr.com/photos/digikam/43485732084/in/dateposted/ Please test with my last installer just posted here : https://files.kde.org/digikam/ Gilles Caulier
Created attachment 114552 [details] Windows Event Log
Same error with digiKam-6.0.0-beta1-20180822T202242-Win64.exe
Ok, We will try another way: Go to your DK install dir. You will found a file digikam.exe and another one named kbuildsycoca5.exe Rename kbuildsycoca5.exe as kbuildsycoca5.old, and start digikam.exe as well. Gilles Caulier
Created attachment 114554 [details] appcrash
Renamed. Digikam crashes on start. Logs attached.
How did you get the log ? From Windows tools ? With the last windows installer build yesterday, you must see a crash wrapper name DrMinGW appear at dysfunction. Look here : https://github.com/jrfonseca/drmingw If not, this want mean that the core Qt5 instance is not yet initialized, and i suspect a side effect with an anti-virus or a protection tools which block access to Windows core API. Typically, the Qt5Core.dll listed in your last trace is used at first time of application life. Of course, i cannot reproduce the dysfunction here with Windows7. I don't have Windows 10 to check. Gilles Caulier
Windows Event Viewer, Application Log, Selected the 3 errors, exported to XML. I only run Malwarebytes & Windows 10 Defender. I get the same APP CRASH with them both disabled.
Just for testing can you download Krita windows installer from here : https://krita.org/en/download/krita-desktop/ Can you start it ? Gilles Caulier
Yes it starts: "Welcome to Krita (x64) 4.1.1 Setup"
Maik, Can you reproduce the dysfunction under Windows 10 ? Gilles
DigiKam-6.0.0 runs very well here under Windows10 in VirtualBox. I'm using Windows10 with version 1709, the current is 1803. I'm going to install the current 1803 version tomorrow. That already kbuildsycoca crashes is very strange. Maik
I am running: Microsoft Windows 10 x64 [Version 10.0.17741.1000], which is 1809.
Nick, I just installed a fresh VM with last Windows 10 rev.1803, and last digiKam 6.0.0 pre-release version from git can be installed and started without any problem. The proof : https://www.flickr.com/photos/digikam/30366688658 https://www.flickr.com/photos/digikam/44185445592 So something special have been changed or installed on your system, which break the compatibility with extra binary... Gilles Caulier
I just did a complete uninstall and deleted all traces of digikam & it's files from my PC (appdata etc). Then did a fresh reinstall with Malwarebytes and Defender turned off. No changes to behaviour. kbuildsycoca5.exe crashes on install, digikam.exe crashes on run.
Well i'm lost here. Without to know the difference between the current official Win10 rev.1803 and your, it's impossible to investigate.
Still no difference with installer compiled today ? https://files.kde.org/digikam/ Gilles Caulier
Same error on install and run. :(
The Windows10 1809 version is a developer preview. You are participating in the Windows10 Preview Build program. Officially, 1809 will be rolled out in October and then in the next 2 months. Hard to say if the problem still exists in the official Windows version and why Krita has no problem at the moment. Maik
Windows 10-1809 October Update is officially released. I have created a new VM and digiKam-6.0.0-beta1 runs without problems here. Maik
I confirm, it's magically fixed in one of the recent builds. No error on install, no error on run. It did reset all my preferences and setup however.