Application: digikam (8.1.0) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.12-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: Trying to generate the digital signatures of my pictures, Digikam crashed. Backend is a remote (lan) Mysql Server, and the pictures are stored in a NFS dir. The crash can be reproduced every time. -- Backtrace (Reduced): #4 __memcpy_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:660 #5 0x00007f9b7bdeb378 in (anonymous namespace)::LoaderExifJpeg::getData() const (this=0x7f9a5401e1d0) at /usr/src/debug/exiv2/exiv2-0.28.0/src/preview.cpp:509 #6 0x00007f9b7bde43b3 in Exiv2::PreviewManager::getPreviewProperties() const (this=this@entry=0x7f9a54018610) at /usr/src/debug/exiv2/exiv2-0.28.0/src/preview.cpp:1018 #7 0x00007f9b816e9b49 in Digikam::MetaEnginePreviews::Private::load(std::unique_ptr<Exiv2::Image, std::default_delete<Exiv2::Image> >) (this=0x7f9a5401e140, image_=std::unique_ptr<Exiv2::Image> = {...}) at /usr/src/debug/digikam/digikam-8.1.0/core/libs/metadataengine/engine/metaengine_previews.cpp:65 #8 0x00007f9b816ea6db in Digikam::MetaEnginePreviews::MetaEnginePreviews(QString const&) (this=0x7f9a88ff7d10, filePath=<optimized out>, this=<optimized out>, filePath=<optimized out>) at /usr/include/c++/13.1.1/bits/unique_ptr.h:197 Reported using DrKonqi
Created attachment 161607 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
It crashes in the Exiv2 library. Please activate internal debugging in the digiKam settings under Miscellaneous->System. Then restart digiKam in the terminal and post the last outputs in the terminal. We may find out the last file that is being processed. Maik
(In reply to Maik Qualmann from comment #2) > It crashes in the Exiv2 library. Please activate internal debugging in the > digiKam settings under Miscellaneous->System. Then restart digiKam in the > terminal and post the last outputs in the terminal. We may find out the last > file that is being processed. > > Maik So these are the last log lines: digikam.metaengine: EXV chunk size: 27697 digikam.metaengine: ExifTool parsed command for action "Load Chunks" 1 properties decoded digikam.metaengine: ExifTool complete "Load Chunks" for "/home/oneko/nas/pictures/revelar/pictures/101CANON/IMG_9203.CR2" digikam.metaengine: Metadata chunk loaded with ExifTool digikam.metaengine: ExifToolProcess::readOutput(): ExifTool command completed digikam.metaengine: ExifTool complete command for action "Load Chunks" with elasped time (ms): 69 digikam.metaengine: EXV chunk size: 26957 digikam.metaengine: ExifTool parsed command for action "Load Chunks" 1 properties decoded digikam.metaengine: ExifTool complete "Load Chunks" for "/home/oneko/nas/pictures/revelar/pictures/101CANON/IMG_9204.CR2" digikam.metaengine: Metadata chunk loaded with ExifTool digikam.metaengine: ExifToolProcess::readOutput(): ExifTool command completed digikam.metaengine: ExifTool complete command for action "Load Chunks" with elasped time (ms): 69 digikam.metaengine: EXV chunk size: 23709 digikam.metaengine: ExifTool parsed command for action "Load Chunks" 1 properties decoded digikam.metaengine: ExifTool complete "Load Chunks" for "/home/oneko/nas/pictures/revelar/pictures/101CANON/IMG_9205.CR2" digikam.metaengine: Metadata chunk loaded with ExifTool digikam.metaengine: ExifToolProcess::readOutput(): ExifTool command completed digikam.metaengine: ExifTool complete command for action "Load Chunks" with elasped time (ms): 68 digikam.metaengine: EXV chunk size: 23449 digikam.metaengine: ExifTool parsed command for action "Load Chunks" 1 properties decoded digikam.metaengine: ExifTool complete "Load Chunks" for "/home/oneko/nas/pictures/revelar/pictures/101CANON/IMG_9206.CR2" digikam.metaengine: Metadata chunk loaded with ExifTool 21 -- exe=/usr/bin/digikam 13 -- platform=xcb 11 -- display=:0 16 -- appname=digikam 17 -- apppath=/usr/bin 9 -- signal=7 11 -- pid=163583 17 -- appversion=8.1.0 20 -- programname=digiKam 31 -- bugaddress=submit@bugs.kde.org KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = digikam path = /usr/bin pid = 163583 KCrash: Arguments: /usr/bin/digikam QSocketNotifier: Invalid socket 38 and type 'Read', disabling... QSocketNotifier: Invalid socket 40 and type 'Read', disabling... QSocketNotifier: Invalid socket 44 and type 'Read', disabling... [warn] epoll_wait: Descriptor de fichero erróneo [warn] epoll_wait: Descriptor de fichero erróneo [warn] epoll_wait: Descriptor de fichero erróneo [warn] epoll_wait: Descriptor de fichero erróneo ... millions of [warn] epoll_wait: Descriptor de fichero erróneo (english: bad file descriptor) This is the last processed picture: https://drive.google.com/file/d/1zgfktX0fr8NIgIrOreUn71cSMXMUuUEw/view?usp=sharing Aparently it's ok, isn't it?
Is this a complete log? For example, I miss a lot of messages from Exiv2. The CR2 file doesn't crash for me here, try to identify the file in question by removing and adding files again. Maik
OnekO; What's about this file using current 8.2.0 AppImage Linux bundle ? It's reproducible ? https://files.kde.org/digikam/ Thanks in advance Gilles Caulier
@Oneko, digiKam 8.3.0 stable version is released and available at usual place : https://www.digikam.org/download/ Can you reproduce the dysfunction on your computer ? Thanks in advance Gilles Caulier
Hi, digiKam 8.5.0. is out with many fixes and improvements. https://www.digikam.org/news/2024-11-16-8.5.0_release_announcement/ This report still valid with this version? Thanks in advance Gilles Caulier
Hi, digiKam 8.6.0 is just released: https://www.digikam.org/news/2025-03-15-8.6.0_release_announcement/ Problem still exists with this version? Thanks in advance Gilles Caulier