Bug 470621 - digikam crashed when applying tag to many pictures on nfs mounted collection
Summary: digikam crashed when applying tag to many pictures on nfs mounted collection
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Engine (other bugs)
Version First Reported In: 8.0.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-06-04 08:13 UTC by Petr Hrasky
Modified: 2023-10-11 05:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 8.2.0
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (66.70 KB, text/plain)
2023-06-04 08:13 UTC, Petr Hrasky
Details
attachment-42011-0.html (1.68 KB, text/html)
2023-06-07 17:37 UTC, Petr Hrasky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Hrasky 2023-06-04 08:13:41 UTC
Application: digikam (8.0.0)

Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.5-200.fc38.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora release 38 (Thirty Eight)"
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
there are more than 600 picture in this album. I applied tag. Digikam crashed slortly after that. I can see the tag is applied to pictures. Collection is on nfs server. Access is from laptop with 5GHz wifi.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  0x00007fdfa8f296ca in Exiv2::DataValue::read(unsigned char const*, long, Exiv2::ByteOrder) () at /lib64/libexiv2.so.27
#6  0x00007fdfa8f96c61 in Exiv2::Internal::TiffReader::readTiffEntry(Exiv2::Internal::TiffEntryBase*) () at /lib64/libexiv2.so.27
#7  0x00007fdfa8f97b12 in Exiv2::Internal::TiffReader::visitMnEntry(Exiv2::Internal::TiffMnEntry*) () at /lib64/libexiv2.so.27
#8  0x00007fdfa8f875cd in Exiv2::Internal::TiffMnEntry::doAccept(Exiv2::Internal::TiffVisitor&) () at /lib64/libexiv2.so.27
#9  0x00007fdfa8f874b8 in Exiv2::Internal::TiffDirectory::doAccept(Exiv2::Internal::TiffVisitor&) () at /lib64/libexiv2.so.27


Reported using DrKonqi
Comment 1 Petr Hrasky 2023-06-04 08:13:42 UTC
Created attachment 159457 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Maik Qualmann 2023-06-04 08:27:12 UTC
It crashes in Exiv2 when trying to read metadata from (probably) a TIFF image. Try to identify the TIFF image by enabling debug output in the terminal and providing the image. If the problem can be reproduced with the Exiv2 CLI tool, the problem must be reported to Exiv2. Which Exiv2 version are you using exactly?

Maik
Comment 3 caulier.gilles 2023-06-04 10:10:48 UTC
In Linux AppImage 8.1.0 pre-release we use last Exiv2 0.28.

If your Fedora package use Exiv2 0.27.x, we recommend to test with the AppImage bundle to see if the problem remain.

Files are there:

https://files.kde.org/digikam/

Gilles Caulier
Comment 4 Petr Hrasky 2023-06-07 17:37:37 UTC
Created attachment 159519 [details]
attachment-42011-0.html

It worked wirth appimage digikam 8,1. It worked when I used rpm digikam 8.0
from fc38 when I attached 1Gbps to laptop with usb-c adapter.

Thanks.

Petr


On Sun, Jun 4, 2023 at 12:10 PM <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=470621
>
> caulier.gilles@gmail.com changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |caulier.gilles@gmail.com
>
> --- Comment #3 from caulier.gilles@gmail.com ---
> In Linux AppImage 8.1.0 pre-release we use last Exiv2 0.28.
>
> If your Fedora package use Exiv2 0.27.x, we recommend to test with the
> AppImage
> bundle to see if the problem remain.
>
> Files are there:
>
> https://files.kde.org/digikam/
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 5 caulier.gilles 2023-10-11 05:01:24 UTC
Not reproducible here when using Exiv2 0.28 or later. Closed...