Bug 507064

Summary: Crash at start due to enabled video hardware acceleration.
Product: [Applications] digikam Reporter: roland.lengauer
Component: Setup-ConfigFilesAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 8.7.0   
Target Milestone: ---   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 8.8.0
Sentry Crash Report:

Description roland.lengauer 2025-07-15 09:49:26 UTC 
KCRASH_DUMP_ONLY=1 digikam
digikam: /usr/lib/libgphoto2_port.so.12: no version information available (required by /usr/lib/libdigikamgui.so.8.7.0)
digikam.facesengine: FaceClassifier::loadTrainingData: exception:  OpenCV(4.12.0) /usr/include/opencv4/opencv2/core/mat.inl.hpp:921: error: (-215:Assertion failed) (unsigned)(pt.x * DataType<_Tp>::channels) < (unsigned)(size.p[1] * channels()) in function 'at'

GBM is not supported with the current configuration. Fallback to Vulkan rendering in Chromium.
qt.multimedia.ffmpeg: Using Qt multimedia with FFmpeg version n7.1.1 GPL version 3 or later
Speicherzugriffsfehler (Speicherabzug geschrieben)

SUMMARY
Unable to start DigiKam, no (re)configuration possible

STEPS TO REPRODUCE
1. update to DigiKam 8.7.0-2 from Digikam 8.6.0
2. MariaDB, Data on NAS
3. activated openCL hardware acceleration
afterwards no start start possible, always crashing (see crash report)

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 

kinfo
Operating System: Manjaro Linux 
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.15.6-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 32 × AMD Ryzen 9 3950X 16-Core Processor
Memory: 125.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4070 Ti


ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2025-07-15 10:24:53 UTC 
The exception in OpenCV will not cause a crash, as it is caught. Please start digiKam with GDB and create a backtrace after the crash by pressing bt+Enter..

A problem with the hardware detection of FFmpeg is conceivable.

You could edit the digikam_systemrc in the ".config" directory and disable OpenCL and video acceleration as a test.

Maik
Comment 2 Maik Qualmann 2025-07-16 16:40:58 UTC 
It was clarified via private email that the cause is the enabled video hardware acceleration. This issue should be reported to Qt Multimedia or FFmpeg.
For new digiKam configurations, we have already disabled video hardware acceleration by default for digiKam-8.7.0. I'm closing the bug for digiKam.

https://invent.kde.org/graphics/digikam/-/commit/f907882a46a7dcf661ea4cbe03d81dd548cabb80

Maik