Bug 507615

Please try the pre-release digiKam-8.8.0 version from here first:

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

Maik

Hi,

yes, this is probably due to the OpenGL usage at startup. Look on this r/digikam thread for the solution:

https://www.reddit.com/r/digiKam/comments/1m676k8/missing_something_really_really_basic_on_setup/

Best regards

Gilles Caulier

(In reply to Maik Qualmann from comment #1)
> Please try the pre-release digiKam-8.8.0 version from here first:
> 
> https://files.kde.org/digikam/
> 
> Maik

Thank you for the suggestion.   I tried that last night before I posted here, and had the same problems with version 8.8.0.

(In reply to caulier.gilles from comment #2)
> Hi,
> 
> yes, this is probably due to the OpenGL usage at startup. Look on this
> r/digikam thread for the solution:
> 
> https://www.reddit.com/r/digiKam/comments/1m676k8/
> missing_something_really_really_basic_on_setup/
> 
> Best regards
> 
> Gilles Caulier

Thank you.  I looked at the reddit, but it doesn't contain a solution.   Are you asking me to create a debug trace file as the next step?  Am I looking for something relating to OpenGL usage?

yes, i propose a solution in reddit, to patch an INI setting file used by digiKam:

// ----------------------------------------------------------------------------------------------------------------------

The problem is know and is relevant of the QtWebEngine component (Chromium based and embedded browser).

Typically Chromium do not detect the GPU acceleration on your Windows and lock tha application. This have been already reported previously.

Solution: in the digikam_systemrc INI config file:

https://docs.digikam.org/en/getting_started/installation.html#configuration-files

... turn on an option about the GPU feature:

Use the software OpenGL rendering: this option will disable the GPU hardware accelerations and switch to a software-emulation for all calls to OpenGL.

https://docs.digikam.org/en/setup_application/miscs_settings.html#system-settings

This is a view of my digikam_systemrc file contents:

[System]
disableOpenCL=true
dnnOpenCLTested=false
enableAIAutoTools=true
enableAesthetic=true
enableAutoTags=true
enableDnnOpenCL=false
enableFaceEngine=true
enableHWTConv=true
enableHWVideo=true
enableLogging=false
enableOpenCL=false
proxyAuth=false
proxyPort=8080
proxyType=0
proxyUrl=
softwareOpenGL=true <==== THIS ONE!!!
useHighDpiPixmaps=false
useHighDpiScaling=false
videoBackend=ffmpeg

// ----------------------------------------------------------------------------------------------------------------------

(In reply to caulier.gilles from comment #5)
> yes, i propose a solution in reddit, to patch an INI setting file used by
> digiKam:
> 
> //
> -----------------------------------------------------------------------------
> -----------------------------------------
> 
> The problem is know and is relevant of the QtWebEngine component (Chromium
> based and embedded browser).
> 
> Typically Chromium do not detect the GPU acceleration on your Windows and
> lock tha application. This have been already reported previously.
> 
> Solution: in the digikam_systemrc INI config file:
> 
> https://docs.digikam.org/en/getting_started/installation.html#configuration-
> files
> 
> ... turn on an option about the GPU feature:
> 
> Use the software OpenGL rendering: this option will disable the GPU hardware
> accelerations and switch to a software-emulation for all calls to OpenGL.
> 
> https://docs.digikam.org/en/setup_application/miscs_settings.html#system-
> settings
> 
> This is a view of my digikam_systemrc file contents:
> 
> [System]
> disableOpenCL=true
> dnnOpenCLTested=false
> enableAIAutoTools=true
> enableAesthetic=true
> enableAutoTags=true
> enableDnnOpenCL=false
> enableFaceEngine=true
> enableHWTConv=true
> enableHWVideo=true
> enableLogging=false
> enableOpenCL=false
> proxyAuth=false
> proxyPort=8080
> proxyType=0
> proxyUrl=
> softwareOpenGL=true <==== THIS ONE!!!
> useHighDpiPixmaps=false
> useHighDpiScaling=false
> videoBackend=ffmpeg
> 
> //
> -----------------------------------------------------------------------------
> -----------------------------------------

Thank you.  The redit link you previously posted didn't send me to a page with a solution.   I'll try to implement what you suggested below.   Whether this helps or not, I had been using the Qt6 version of 8.6.0 prior to this without issue.

I believe I made the correct changes to the digikam_systemrc file, without any success.  For now I'm going to stick with 8.6.0 as I have a project I need to work on, but I'll try to debug the issues with 8.7.0 and 8.8.0 time permitting.  Thanks for the help.

@Alan,

The digiKam 8.8.0 pre-release Windows installer will be updated from Qt framework 6.8.3 to 6.9.0 in one hour. I removed the NVIDIA drivers from this bundle. The file will be available soon at this place:

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

Please test give us a feedback to see if the dysfunction still reproducible.
Thanks in advance

Gilles Caulier

(In reply to caulier.gilles from comment #8)
> @Alan,
> 
> The digiKam 8.8.0 pre-release Windows installer will be updated from Qt
> framework 6.8.3 to 6.9.0 in one hour. I removed the NVIDIA drivers from this
> bundle. The file will be available soon at this place:
> 
> https://files.kde.org/digikam/
> 
> Please test give us a feedback to see if the dysfunction still reproducible.
> Thanks in advance
> 
> Gilles Caulier

Gilles,
Was this supposed to be directed at me, or was this supposed to be in response to a different thread?
Thanks,
Marc

yes to you. I'm wrong with the @ sequence from my previous message...

(In reply to caulier.gilles from comment #10)
> yes to you. I'm wrong with the @ sequence from my previous message...

Thanks for clarifying.  I will look out for the 8.8.0 installer with today's time stamp.

I have few internet dysfunctions at home today, but it's back. Install 8.8.0 will be online this evening...

Gilles

(In reply to caulier.gilles from comment #10)
> yes to you. I'm wrong with the @ sequence from my previous message...

(In reply to mlavine from comment #9)
> (In reply to caulier.gilles from comment #8)
> > @Alan,
> > 
> > The digiKam 8.8.0 pre-release Windows installer will be updated from Qt
> > framework 6.8.3 to 6.9.0 in one hour. I removed the NVIDIA drivers from this
> > bundle. The file will be available soon at this place:
> > 
> > https://files.kde.org/digikam/
> > 
> > Please test give us a feedback to see if the dysfunction still reproducible.
> > Thanks in advance
> > 
> > Gilles Caulier
> 
> Gilles,
> Was this supposed to be directed at me, or was this supposed to be in
> response to a different thread?
> Thanks,
> Marc

(In reply to caulier.gilles from comment #8)
> @Alan,
> 
> The digiKam 8.8.0 pre-release Windows installer will be updated from Qt
> framework 6.8.3 to 6.9.0 in one hour. I removed the NVIDIA drivers from this
> bundle. The file will be available soon at this place:
> 
> https://files.kde.org/digikam/
> 
> Please test give us a feedback to see if the dysfunction still reproducible.
> Thanks in advance
> 
> Gilles Caulier

I downloaded 8.8.0 and installed it.  The first time it tried to launch 8.8.0, it crashed without fully loading.  The second time it started to load and again got stuck on the loading tools section.   I uninstalled and reinstalled a second time, and observed the same behaviour.

Unfortunately, switching to Software OpenGL via the GUI in the previous (working) version, or via Notepad++ per the config outline above, do not seem to alter the behavior. I see the standard 'welcome' boot screen with the familiar textual state info and the dot indicators, and then the app simply closes down.

So, reverting to the version which included the Nvidia drivers etc- as that seemed to work with or without hardware OpenGL etc.

Roland

(In reply to Roland from comment #14)
> Unfortunately, switching to Software OpenGL via the GUI in the previous
> (working) version, or via Notepad++ per the config outline above, do not
> seem to alter the behavior. I see the standard 'welcome' boot screen with
> the familiar textual state info and the dot indicators, and then the app
> simply closes down.
> 
> So, reverting to the version which included the Nvidia drivers etc- as that
> seemed to work with or without hardware OpenGL etc.
> 
> Roland

I tested this and I can confirm this.
digiKam-8.8.0-20250817T162413-Qt6-Win64.exe doesnt start even after modifying the configuration file.
I use Intel video card.

(In reply to Peter from comment #15)
> (In reply to Roland from comment #14)
> > Unfortunately, switching to Software OpenGL via the GUI in the previous
> > (working) version, or via Notepad++ per the config outline above, do not
> > seem to alter the behavior. I see the standard 'welcome' boot screen with
> > the familiar textual state info and the dot indicators, and then the app
> > simply closes down.
> > 
> > So, reverting to the version which included the Nvidia drivers etc- as that
> > seemed to work with or without hardware OpenGL etc.
> > 
> > Roland
> 
> I tested this and I can confirm this.
> digiKam-8.8.0-20250817T162413-Qt6-Win64.exe doesnt start even after
> modifying the configuration file.
> I use Intel video card.

I've since downloaded version digiKam-8.8.0-20250928T170145-Qt6-Win64 and it loads successfully.