Created attachment 150158 [details] Edited transcript of GDB session with backtrace STEPS TO REPRODUCE 1. Build digikam and its KDE dependencies with `kdesrc-build`. Specifically, today I did `kdesrc-build --refresh-build digikam`, then after it failed due to lack of qt5-networkauth, I installed that and ran `kdesrc-build --refresh-build --resume-from digikam digikam`. 2. Run it with `(source build/digikam/prefix.sh && digikam)` (from `~/kde`). (I don’t know if this is the recommended way to run it, but `kdesrc-run digikam` just printed “"kdesrc-build-data" file is not available. Exit now.”) 3. It segfaults every time after the splash screen appears (backtrace attached). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95.0* Qt Version: 5.15.5 Kernel Version: 5.17.15-1-MANJARO (64-bit) Graphics Platform: X11 *including this for completeness, but I assume building with kdesrc-build causes the app to use a bleeding-edge version. digiKam version: revision 5e4b5e25ec (8.0.0-git) ADDITIONAL INFORMATION I have built digiKam several times before getting around to filing a bug report and this happened every time I got it to build. The digikam package from Manjaro and the flatpak package from distribute.kde.org seem to work fine. I’m guessing the component based on information from the backtrace.
The crash can hardly be explained programmatically, since we are checking whether we are getting a JPEG export widget. The only explanation is that you still have a 8.0.0 series jpeg plugin in the system before we introduced the export widget function. Two possibilities: - Do a full clean build. - Check if the DImg_JPEG_Plugin.so file is duplicated in your system. Maik
By the way, it doesn't just have to be the Jpeg DImg plugin twice, it can also be any other plugin. The usual way to build digiKam is to run: $ ./bootstrap.linux $ cd build $ make $ make install
@bethge931@protonmail.com Do you seen the 2 last comments from Maik ? Gilles Caulier
Not reproducible at all. Check your system as explained by Maik in comments. Closed.