Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57830 - [digikam] 5.8.0-1 Segfaults when using facial recognition

Attached to Project: Arch Linux
Opened by Kris Scott (syntobu) - Tuesday, 13 March 2018, 22:51 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 14 March 2018, 22:21 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ronald van Haren (pressh)
Antonio Rojas (arojas)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When trying to recognize faces in Digikam, the program crashes with a segfault

Steps to produce:

1. add some photos to your library
2. click the people button, select "scan collection for faces"
3. Choose "Detect and recognize faces," click Scan

The cause appears to be some incompatibility with libstdc++

std::_Rb_tree_increment (__x=0x52)
at /build/gcc/src/gcc/libstdc++-v3/src/c++98/tree.cc:85
85 /build/gcc/src/gcc/libstdc++-v3/src/c++98/tree.cc: No such file or directory.


Attached is a full backtrace of the crash
   gdb.log (2.6 KiB)
This task depends upon

Closed by  Antonio Rojas (arojas)
Wednesday, 14 March 2018, 22:21 GMT
Reason for closing:  Fixed
Additional comments about closing:  digikam 5.8.0-2
Comment by Antonio Rojas (arojas) - Tuesday, 13 March 2018, 23:16 GMT
Already known upstream https://bugs.kde.org/show_bug.cgi?id=390136. Don't expect them to do anything about it though. For digikam developers, bugs that aren't reproducible in their appimage just don't exist.
Comment by Antonio Rojas (arojas) - Wednesday, 14 March 2018, 12:56 GMT
May actually be fixed already, please test 5.8.0-2
Comment by Kris Scott (syntobu) - Wednesday, 14 March 2018, 21:46 GMT
Yes, appears to be fixed in 5.8.0-2

Loading...