Re: DK 8.8 latest does not start on Win11

So it looks like the problem is with the shortcut configuration of 
digiKam (I have it pinned to Taskbar). The problem seems to be the 
"Start in" parameter, because Windows reports that the path is not 
valid. Original it was "C:\Program Files\digiKam\bin\" and this 
directory really doesn't exist on my installation. So I went and change 
that to "C:\Program Files\digiKam\" and now DK starts even if I click on 
the icon in the Taskbar.
I don't know if this is the right way to correct this issue but at the 
moment I can use  the latest version of DK normally.



Regards,
Andrej

On 20/08/2025 21:08, Andrej Valencic wrote:
> Well this is strange.
>
> If I run it by clicking on the icon (from Start menu, Desktop or 
> Taskbar) it still does not run - the log is the same as before.
>
> But...
> when I tried and run it from the command line in PowerShell - like PS: 
> & 'C:\Program Files\digiKam\digikam.exe' - to my big surprise it runs 
> and looks like it's working (I only tested some basic edits). So the 
> log from this successful operation is included - if it helps somehow.
>
>
> Regards,
> Andrej
>
> On 20/08/2025 20:44, Gilles Caulier wrote:
>> Hi,
>>
>> Can you test with the new Qt6 Windows bundles version 8.8.0 just
>> published online at usual place ?
>>
>> Best
>>
>> Gilles Caulier
>>
>> Le mer. 20 août 2025 à 10:49, Andrej Valencic
>> <[email protected]> a écrit :
>>> That's what I've already included as an attachment in the previous
>>> message - DK.zip
>>>
>>> Regards,
>>> Andrej
>>>
>>> On 20/08/2025 10:46, Gilles Caulier wrote:
>>>> We need the debug traces captured by DebugView at startup of 
>>>> digiKam...
>>>>
>>>> Gilles Caulier
>>>>
>>>> Le mer. 20 août 2025 à 10:43, Andrej Valencic
>>>> <[email protected]> a écrit :
>>>>> It's the same as before (see attachment) - no obvious error 
>>>>> indication
>>>>> that I could see.
>>>>>
>>>>> This is what my systemrc contains::
>>>>>
>>>>> [System]
>>>>> useHighDpiScaling=true
>>>>> useHighDpiPixmaps=true
>>>>> disableOpenCL=true
>>>>> enableLogging=true
>>>>> enableFaceEngine=false
>>>>> enableAesthetic=false
>>>>> enableAutoTags=false
>>>>> proxyUrl=
>>>>> proxyPort=8080
>>>>> proxyType=0
>>>>> proxyAuth=false
>>>>> softwareOpenGL=false
>>>>> disableHWConv=false
>>>>> videoBackend=ffmpeg
>>>>> enableOpenCL=false
>>>>> enableHWVideo=true
>>>>> enableHWTConv=true
>>>>> enableAITools=true
>>>>> deleteOldDNNFiles=true
>>>>> enableAIAutoTools=true
>>>>> enableDnnOpenCL=false
>>>>> dnnOpenCLTested=false
>>>>> softwareOpenGL=true
>>>>>
>>>>>
>>>>> Regards,
>>>>> Andrej
>>>>>
>>>>> On 20/08/2025 10:23, Gilles Caulier wrote:
>>>>>> If you install debugview and start digiKAm, what do you seen as 
>>>>>> debug
>>>>>> trace. See the notice here :
>>>>>>
>>>>>> https://www.digikam.org/contribute/#windows-host
>>>>>>
>>>>>> Gilles Caulier
>>>>>>
>>>>>> Le mer. 20 août 2025 à 10:20, Andrej Valencic
>>>>>> <[email protected]> a écrit :
>>>>>>> I did the recommended changes to digikam_systemrc but 
>>>>>>> unfortunately that
>>>>>>> didn't help - DK still doesn't run.
>>>>>>> Any other things I might try?
>>>>>>>
>>>>>>> Regards,
>>>>>>> Andrej
>>>>>>>
>>>>>>> On 20/08/2025 09:30, Gilles Caulier wrote:
>>>>>>>> Le mer. 20 août 2025 à 09:23, Andrej Valencic
>>>>>>>> <[email protected]> a écrit :
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> I just downloaded the latest build 8.8 for Windows (dated 
>>>>>>>>> 2025-08-20
>>>>>>>>> 04:49) and it doesn't start anymore. When i run DK it just 
>>>>>>>>> displays the
>>>>>>>>> start flash image and then closes. Some older releas was 
>>>>>>>>> working without
>>>>>>>>> problem.
>>>>>>>>>
>>>>>>>>> I tried the debug version as well so I'm including the log.
>>>>>>>>>
>>>>>>>>> P.S. I noticed that this version is much smaller then it was a 
>>>>>>>>> couple of
>>>>>>>>> releases earlier (now 200+ MB, before 600+ MB). Could it be a 
>>>>>>>>> problem
>>>>>>>>> with included libraries?
>>>>>>>> No. It's the huge NVIDIA SDK previously embedded which is now 
>>>>>>>> dropped.
>>>>>>>>
>>>>>>>> Your problem is relevant to the OpenGL support. Turn on the 
>>>>>>>> software
>>>>>>>> OpenGL support as explained here :
>>>>>>>>
>>>>>>>> https://bugs.kde.org/show_bug.cgi?id=507615#c5
>>>>>>>>
>>>>>>>> Best regards
>>>>>>>>
>>>>>>>> Gilles Caulier