https://bugs.kde.org/show_bug.cgi?id=409437
caulier.gil...@gmail.com changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=409437
--- Comment #14 from caulier.gil...@gmail.com ---
digiKam 7.0.0-beta1 is ready for testing :
https://download.kde.org/unstable/digikam/
In this release, the Faces Management pipeline receive a lots of patches to
increase stability and prevent crash. Yo
https://bugs.kde.org/show_bug.cgi?id=409437
--- Comment #13 from Maik Qualmann ---
I found this:
https://answers.opencv.org/question/147932/how-to-change-opencl-device/
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409437
--- Comment #12 from Daniel Rowe ---
So I reinstalled the OpenCL package and now when I run I get the AMD GPU as the
default GPU device which is on this system as well now it runs fine. What's
annoying is why is the AMD GPU now the default and how this
https://bugs.kde.org/show_bug.cgi?id=409437
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com,
https://bugs.kde.org/show_bug.cgi?id=409437
--- Comment #10 from Maik Qualmann ---
Ok, thanks for the feedback. So the OpenCL driver for your Intel hardware is
broken. Here with the AMD GPU I can not reproduce a crash. I will do a
benchmark to see how much the use of OpenCL actually brings. I wil
https://bugs.kde.org/show_bug.cgi?id=409437
Rex Dieter changed:
What|Removed |Added
CC||rdie...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=409437
--- Comment #9 from Daniel Rowe ---
I confirm that removing OpenCL packages form my system does indeed stop the
crash.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409437
--- Comment #8 from Maik Qualmann ---
Created attachment 121329
--> https://bugs.kde.org/attachment.cgi?id=121329&action=edit
disableOpenCL.patch
This is a first test patch to disable OpenCL at runtime. This must be done in
every thread. At present,
https://bugs.kde.org/show_bug.cgi?id=409437
--- Comment #7 from Maik Qualmann ---
It is probably possible since OpenCV 3 to disable OpenCL during runtime. I will
test it.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409437
--- Comment #6 from Daniel Rowe ---
Ok I'll cross reference this bug to the Fedora bug that I raised.
I'll also update this if I find a solution.
Thanks for your help.
Just out of interest why would hardware acceleration cause it to break?
--
You a
https://bugs.kde.org/show_bug.cgi?id=409437
--- Comment #5 from Maik Qualmann ---
Yes, OpenCL hardware acceleration is active. I'm sure it's the cause of the
crash. Here on openSUSE Tumbleweed (developer version) OpenCL is disabled. We
at digiKam can not change anything from here. My recommendati
https://bugs.kde.org/show_bug.cgi?id=409437
--- Comment #4 from Daniel Rowe ---
opencv_version --hw --opencl
3.4.4
[ INFO:0] Initialize OpenCL runtime...
OpenCL Platforms:
Intel Gen OCL Driver
iGPU: Intel(R) HD Graphics Kabylake Halo GT2 (OpenCL 2.0 beignet 1.3)
Clover
dG
https://bugs.kde.org/show_bug.cgi?id=409437
--- Comment #3 from Maik Qualmann ---
After the backtrace, it looks like the Fedora OpenCV packages are compiled with
OpenCL. Please post the output for "opencv_version --hw --opencl".
Maik
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=409437
Maik Qualmann changed:
What|Removed |Added
Version|6.2.0 |6.1.0
--- Comment #2 from Maik Qualmann ---
Af
https://bugs.kde.org/show_bug.cgi?id=409437
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
16 matches
Mail list logo
