SUMMARY I use LINUX MAGEIA8 with plasma5 desktop 5.13.8-server1.mga8 . I have a HD 200G (only used for my pictures) with 110G free Digikam 7.3(64 bits appimage) was working good but i think it's could be a database problem (mysql) due to saturation ? STEPS TO REPRODUCE 1. Start with "Albums" 2. Wait while looking for new albums: everything seems correct but after 60% digikam 7.3 disappear (closed) 3. But if i use digikam 7.1.0 it's works correctly . OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
sometimes idigikam start ang go to 100% if I go to the people / facial recognition module and try to identify faces from the first modifications everything stops and digikam 7.3.0 closes
Which MySQL version do you use exactly? Maik
I use LINUX Mageia8 64bits desktop 5.13.8-server1.mga8 KDE plasma 5.20.4 KDE Framework 5.76.0 QT 5.15.2 Processeur Intel core 4 X I5 7400 CPU 3.00G mysql Ver 15.1 Distrib 10.5.12-MariaDB, for Linux (x86_64) using readline 5.1 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Ok, the MySQL version is not the problem, then we need a GDB backtrace. Download the AppImage in the debug version and start it with the "debug" option, if the crash occurred, enter "bt" in the terminal and post the output. Maik
One problem is, the face database is broken, you have to remove all tables and start a new one: -------------------------------- Digikam::FaceDbSchemaUpdater::startUpdates: DBFaceVersion not available! Giving up schema upgrading. Digikam::FaceDbAccess::checkReadyForUse: Face database: cannot process schema initialization -------------------------------- This seems to be the cause, you have a defective JPEG2000 image that causes Exiv2 to crash: -------------------------------- Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot load metadata from file with Exiv2 backend: /run/media/jplajoie/PHOTOS/PHOTOS/ocean indien/M ayotte/1995/Au rocher2.jp2 (Error # 59 : "corrupted image metadata" -------------------------------- Can you provide the broken image to reproduce the crash? DigiKam will also not work with the defective face database. Maik
exactly there was a corrupted image. maybe it would be an up if digikam recognized bad files and ignored them. I recreate the database and keep you informed of the rest.
It would be nice if we could have the corrupt image to reproduce the problem. If not publicly, on my private mail. Maik
Created attachment 142809 [details] Au rocher1.jpg good morning ok the corrupt file was "au rocher2.jp2" and the good file was "au rocher1.jpg" I restarted digikam with a new database for the moment it works, but I have to rebuild the whole database and it will take a long time! I will keep you informed i whish you a good weekend jp lajoie Le 23/10/2021 à 21:43, Maik Qualmann a écrit : > https://bugs.kde.org/show_bug.cgi?id=444220 > > --- Comment #7 from Maik Qualmann <metzpinguin@gmail.com> --- > It would be nice if we could have the corrupt image to reproduce the problem. > If not publicly, on my private mail. > > Maik >
Created attachment 142810 [details] Au rocher2.jp2
The cause is clear, the crash can be reproduced with the digiKam-7.3.0 AppImage. An older libjasper library is still used in digiKam-7.3.0 AppImage. The libjasper library is responsible for JPEG2000 images and many problems have been fixed in the last versions. Here with my native developer version there are no more problems with the broken image and libjasper-2.0.33. Thanks for your help in finding the cause. Maik
Currently libjasper 2.0.32 is used to build the AppImage bundle. Do i need to update to last 2.0.33 ? Gilles
it's a pleasure if we can help tks jp lajoie Le 24/10/2021 à 11:10, Maik Qualmann a écrit : > --- Comment #10 from Maik Qualmann<metzpinguin@gmail.com> --- > The cause is clear, the crash can be reproduced with the digiKam-7.3.0 > AppImage. An older libjasper library is still used in digiKam-7.3.0 AppImage. > The libjasper library is responsible for JPEG2000 images and many problems have > been fixed in the last versions. Here with my native developer version there > are no more problems with the broken image and libjasper-2.0.33. > > Thanks for your help in finding the cause.
Hi Gilles, the digiKam-7.3.0 AppImage uses libjasper-1.900.23. The last pre-release AppImage digiKam-7.4.0 uses libjasper-2.0.27 and no longer crashes, we can close the bug. Maik