SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Whenever digikam tries to update its knowledge about faces, it crashes with the following console output: /usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = float; _Alloc = std::allocator<float>; reference = float&; size_type = long unsigned int]: Assertion '__n < this->size()' failed. fish: Job 1, 'digikam' terminated by signal SIGABRT (Abort) "Whenever it tries to update its knowledge" comprises the following situations (and maybe more): - I manually label a face in a picture with Ctrl+Mouse. As soon as i hit enter after having typed the name of the person, the program crashes. - I right click on a collection or subcollection and in the context menu, click on "Scan for faces' STEPS TO REPRODUCE 1. Open digikam 2. Right-click any collection or sub-collection from your "Albums" tab. 3. In the context menu, click on "Scan for faces" OBSERVED RESULT The program crashes EXPECTED RESULT It scans for faces without crashing SOFTWARE/OS VERSIONS Arch Linux gcc v12.2.1 Qt Version: 5.15.8 ADDITIONAL INFORMATION
The cause is a bug in the release version of OpenCV-4.7.0. The problem has already been fixed in the current master version of OpenCV. We added a workaround for digiKam-7.10.0 to bypass the bug in OpenCV-4.7.0. https://invent.kde.org/graphics/digikam/-/commit/f2f86c3c6719e4ea0bc7de95ce1ae33e8c45495e Maik
This evening, i will rebuild all bundles including last Maik changes Gilles
(In reply to Maik Qualmann from comment #1) > The cause is a bug in the release version of OpenCV-4.7.0. The problem has > already been fixed in the current master version of OpenCV. We added a > workaround for digiKam-7.10.0 to bypass the bug in OpenCV-4.7.0. > > https://invent.kde.org/graphics/digikam/-/commit/ > f2f86c3c6719e4ea0bc7de95ce1ae33e8c45495e > > Maik Thanks for your quick reply, looking forward to the new build!
Again, for the avoidance of doubt: Gilles creates a new AppImage, but it is not affected since we are still using OpenCV-4.6.0. Here Archlinux would have to create a new patched version. Maik
(In reply to Maik Qualmann from comment #4) > Again, for the avoidance of doubt: Gilles creates a new AppImage, but it is > not affected since we are still using OpenCV-4.6.0. Here Archlinux would > have to create a new patched version. > > Maik Ah okay, thanks for clarifying! So i'll wait for the patch to the arch opencv package.
*** Bug 465038 has been marked as a duplicate of this bug. ***