Created attachment 154629 [details] syslog for starting and crashing of appimage 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 *** STEPS TO REPRODUCE 1. Select Run on appimage and click 2. 3. OBSERVED RESULT Splash screen comes up and then dissappears core dump listed in syslog EXPECTED RESULT Program opens after splash screen SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux LAP2 5.15.0-56-generic #62~20.04.1-Ubuntu SMP Tue Nov 22 21:24:20 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Cannot figure out how to get a backtrace for this . Attached syslog output
Please download the debug AppImage and start it in the terminal with the "debug" option. After startup type "r" + enter to start digiKam eiter, after the crash type "bt" + enter and post the output that is printed. The crash occurs on an empty QList, it is important to determine the location in the code. Maik
Upgraded from 7.8 to 7.9. Deleted .config/digikamrc .config/digikam_systemrc and Digikam 7.9 started up right away. Required reconfiguration.
Do you still have the digiKamrc from digiKam-7.8.0 and can you send it to me? Maik
Stupidly I deleted both. I should have just renamed them.
Git commit 47ea5b163ec236e3a0a1ca9f12af50cfa32d00a7 by Maik Qualmann. Committed on 18/12/2022 at 09:05. Pushed by mqualmann into branch 'qt5-maintenance'. better check for correct size of the rating container FIXED-IN: 7.10.0 M +2 -1 NEWS M +0 -1 core/libs/metadataengine/dmetadata/dmetadata_labels.cpp M +7 -9 core/libs/metadataengine/dmetadata/dmetadatasettingscontainer.cpp https://invent.kde.org/graphics/digikam/commit/47ea5b163ec236e3a0a1ca9f12af50cfa32d00a7
Unfortunately, we can no longer reproduce the crash. But because of damaged settings of the extended metadata, a crash would be conceivable. If the problem can be reproduced again, reopen the bug report. Maik