*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY After updating to 8.5.0, facial recognition fails to work, with the following error in the terminal output when attempting: [ERROR:0@33.063] global ./modules/dnn/src/net_impl.cpp (1168) getLayerShapesRecursively OPENCV/DNN: [Eltwise]:(onnx_node!Add_44): getMemoryShapes() throws exception. inputs=2 outputs=1/1 blobs=0 [ERROR:0@33.063] global ./modules/dnn/src/net_impl.cpp (1174) getLayerShapesRecursively input[0] = [ 1 64 38 17 ] [ERROR:0@33.063] global ./modules/dnn/src/net_impl.cpp (1174) getLayerShapesRecursively input[1] = [ 1 64 38 16 ] [ERROR:0@33.063] global ./modules/dnn/src/net_impl.cpp (1178) getLayerShapesRecursively output[0] = [ 1 64 38 17 ] [ERROR:0@33.063] global ./modules/dnn/src/net_impl.cpp (1184) getLayerShapesRecursively Exception message: OpenCV(4.6.0) ./modules/dnn/src/layers/eltwise_layer.cpp:251: error: (-215:Assertion failed) inputs[vecIdx][j] == inputs[i][j] in function 'getMemoryShapes' was running mariadb local backend, rebuilt training data, no change. Re-downloaded models, no change. Converted to SQLite with WAL, and no recognition database, no change. STEPS TO REPRODUCE 1. Update to 8.5.0 2. Run Scan For Faces on a file, folder, or entire album 3. OBSERVED RESULT error message above appears for each file you attempt to scan (Scan 1, get 1, scan 36 get 36 errors) EXPECTED RESULT Facial Recognition works. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
The Neon OpenCV packages are probably too old, use our AppImage. The bug has already been reported for Neon. Maik
*** This bug has been marked as a duplicate of bug 498024 ***
Fixed with bug 498024