https://bugs.kde.org/show_bug.cgi?id=507615
caulier.gil...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |caulier.gil...@gmail.com
--- Comment #5 from caulier.gil...@gmail.com ---
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
//
----------------------------------------------------------------------------------------------------------------------
--
You are receiving this mail because:
You are watching all bug changes.
