SUMMARY using bundle appimage weekly snapshot STEPS TO REPRODUCE 1. random, while doing face recognition or simply manipulating pictures in albums. OBSERVED RESULT digikam crashing #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65 #1 0x00007ffff7dc3799 in ?? () from /lib/x86_64-linux-gnu/libudev.so.0 #2 0x00007ffff7dc3931 in ?? () from /lib/x86_64-linux-gnu/libudev.so.0 #3 0x00007ffff7dc3aac in ?? () from /lib/x86_64-linux-gnu/libudev.so.0 #4 0x00007ffff7dc5ca3 in udev_device_get_subsystem () from /lib/x86_64-linux-gnu/libudev.so.0 #5 0x00007fffe2508903 in udev_monitor_receive_device () from /tmp/.mount_digikakTIeks/usr/lib/libudev.so.1 #6 0x00007fffe7182a62 in ?? () from /tmp/.mount_digikakTIeks/usr/lib/libQt5WebEngineCore.so.5 #7 0x00007fff9c002b00 in ?? () #8 0x00007fffb4d0e410 in ?? () #9 0x0000000000cdada8 in ?? () #10 0x0000000000000000 in ?? () EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: using gnome (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.54 Qt Version: 5.11.3 ADDITIONAL INFORMATION
There is no digiKam symbols visible in your trace. 1/ donwload the debug version of AppImage 2/ run the bundle with -debug argument. 3/ when it crash in debugger, enter "bt" to get detailed backtrace. Gilles Caulier
Is it better like this ?: ... many (too many) RST like this (relatively new behavior) unknown: RST3 ( 3 ) unknown: RST4 ( 3 ) unknown: RST5 ( 3 ) unknown: RST6 ( 3 ) unknown: RST7 ( 3 ) unknown: RST0 ( 3 ) unknown: RST1 ( 3 ) unknown: RST2 ( 3 ) unknown: End Of Image ( 1 ) Digikam::ItemLister::listImageTagPropertySearch: Search result: 12777 Digikam::ActionThreadBase::cancel: Cancel Main Thread [Thread 0x7fff7d5eb700 (LWP 5131) exited] Digikam::ActionThreadBase::slotJobFinished: One job is done Digikam::ActionThreadBase::cancel: Cancel Main Thread [Thread 0x7fff65172700 (LWP 5132) exited] Digikam::CollectionScanner::completeHistoryScanning: items to tag () Digikam::CollectionScanner::completeScan: Complete scan took: 13290 msecs. Digikam::adjustedEnvironmentForAppImage: Adjusting environment variables for AppImage bundle [Detaching after fork from child process 5133] Digikam::DNotificationWrapper: Event is dispatched to desktop notifier through DBUS Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using 12 CPU core to run threads [New Thread 0x7fff65172700 (LWP 5137)] Digikam::ActionThreadBase::run: Action Thread run 1 new jobs [New Thread 0x7fff7d5eb700 (LWP 5138)] Digikam::ActionThreadBase::slotJobFinished: One job is done [Thread 0x7fff65172700 (LWP 5137) exited] Digikam::ActionThreadBase::cancel: Cancel Main Thread [Thread 0x7fff7d5eb700 (LWP 5138) exited] [Thread 0x7fffa67fc700 (LWP 5064) exited] [Thread 0x7fffb4d0f700 (LWP 5060) exited] [Thread 0x7fffb5d11700 (LWP 5058) exited] Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using 12 CPU core to run threads [New Thread 0x7fffb5d11700 (LWP 5165)] Digikam::ActionThreadBase::run: Action Thread run 1 new jobs [New Thread 0x7fffb4d0f700 (LWP 5166)] Digikam::ActionThreadBase::slotJobFinished: One job is done Digikam::ActionThreadBase::cancel: Cancel Main Thread [Thread 0x7fffb5d11700 (LWP 5165) exited] [Thread 0x7fffb4d0f700 (LWP 5166) exited] [Thread 0x7fff67fff700 (LWP 5097) exited] [Thread 0x7fff7ddec700 (LWP 5090) exited] [Thread 0x7fff7edee700 (LWP 5091) exited] [Thread 0x7fffa7fff700 (LWP 5061) exited] [New Thread 0x7fffa7fff700 (LWP 5447)] [Thread 0x7fffa7fff700 (LWP 5447) exited] [New Thread 0x7fffa7fff700 (LWP 5526)] Thread 14 "ThreadPoolForeg" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffa6ffd700 (LWP 5063)] __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65 65 ../sysdeps/x86_64/multiarch/strlen-avx2.S: Aucun fichier ou dossier de ce type. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65 #1 0x00007ffff7dc3799 in ?? () from /lib/x86_64-linux-gnu/libudev.so.0 #2 0x00007ffff7dc3931 in ?? () from /lib/x86_64-linux-gnu/libudev.so.0 #3 0x00007ffff7dc3aac in ?? () from /lib/x86_64-linux-gnu/libudev.so.0 #4 0x00007ffff7dc5ca3 in udev_device_get_subsystem () from /lib/x86_64-linux-gnu/libudev.so.0 #5 0x00007fffe2508903 in udev_monitor_receive_device () from /tmp/.mount_digikaWEJick/usr/lib/libudev.so.1 #6 0x00007fffe7182a62 in ?? () from /tmp/.mount_digikaWEJick/usr/lib/libQt5WebEngineCore.so.5 #7 0x0000000000000000 in ?? () (gdb)
No more suitable information. Can you give me the full backtrace from the console, including all command lines used to run digiKam ? Gilles Caulier
Created attachment 129016 [details] console trace shell command: ./digikam-7.0.0-rc-20200601T143303-x86-64-debug.appimage debug > debugtrace.txt
Did I provide enough information ? If not, please be more detailed on the procedure, I think I followed instructions as document. Regards Aymeric
Well, there is nothing we can do about a crash within QWebEngine. The function "udev_device_get_subsystem()" probably returns an empty string in your system. Which then leads to a crash. Do you use Wayland in Debian? Maik
a echo $XDG_SESSION_TYPE returns x11, so not wayland Should I report this bug to QT ?
Hi, Yes, you can report this dysfunction to Qt team. Check well if no other one file already exists on this topic. If yes, just append a comment with a link to this entry. Best Gilles Caulier
Note : I'm surpized to see Qt 5.11.3 version, as i ported DK AppImage to last 5.14.2. Please try with last weekly bundle available here : https://files.kde.org/digikam/ Gilles Caulier
Hi, Can you check if this crash still exist with last weekly AppImage build available here : https://files.kde.org/digikam/ Thanks in advance Gilles Caulier
Hi, Seems overall more stable but I could still encounter same bug, randomly. I uploaded latest trace. command: ./digikam-7.0.0-20200713T054546-x86-64-debug.appimage debug > debugtrace.txt Aymeric
Created attachment 130128 [details] trace 20200713
digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier
digiKam 7.2.0 official release is published with more than 360 files closed from bugzilla: https://www.digikam.org/news/2021-03-22-7.2.0_release_announcement/ Can you reproduce the dysfunction with this version ? Thanks in advance for your feedback Gilles Caulier
With digiKam-7.2.0-x86-64-debug.appimage, I have : Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile. unknown: End Of Image ( 1 ) Digikam::StackedView::setViewMode: Stacked View Mode : 1 [New Thread 0x7fff64ff9700 (LWP 1939)] Thread 12 "ThreadPoolForeg" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff9e7fc700 (LWP 20499)] __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65 65 ../sysdeps/x86_64/multiarch/strlen-avx2.S: Aucun fichier ou dossier de ce type. (gdb) bt #0 0x00007ffff3a2b181 in __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65 #1 0x00007ffff7dc3799 in () at /lib/x86_64-linux-gnu/libudev.so.0 #2 0x00007ffff7dc3931 in () at /lib/x86_64-linux-gnu/libudev.so.0 #3 0x00007ffff7dc3aac in () at /lib/x86_64-linux-gnu/libudev.so.0 #4 0x00007ffff7dc5ca3 in udev_device_get_subsystem () at /lib/x86_64-linux-gnu/libudev.so.0 #5 0x00007fffe2a1e903 in udev_monitor_receive_device () at /tmp/.mount_digiKaern6cF/usr/lib/libudev.so.1 #6 0x00007fffe796ba62 in () at /tmp/.mount_digiKaern6cF/usr/lib/libQt5WebEngineCore.so.5 #7 0x00007fff840029c0 in () #8 0x00007fff9e7fb410 in () #9 0x00007fff90001cc8 in () #10 0x0000000000000000 in () I will switch to Bullseye, so many it will disappear with newer version of QT
With next digiKam 7.4.0 release, AppImage bundle is compiled using a more recent Linux Mageia 7.1 host. Last stable Qt 5.15.2 and KF5 5.84 are used. ImageMagick codec 7 and libav 58 (ffmpeg) are used to supports extra image and video formats. https://i.imgur.com/XV1tZkL.png Please check if problem still reproducible with this version available as pre-release here: https://files.kde.org/digikam/ Gilles Caulier
Americ, Stable digiKam 7.4.0 AppImage is published. Please check if problem is reproducible. Thanks in advance Gilles Caulier
I checked with version 7.4 and no more issue, very stable. Ticket can be closed.
Thanks for the feedback. Maik