Bug 512625 - Crash in libexiv via KExiv2Iface::KExiv2::load
Summary: Crash in libexiv via KExiv2Iface::KExiv2::load
Status: RESOLVED UPSTREAM
Alias: None
Product: libkexiv2
Classification: Frameworks and Libraries
Component: General (other bugs)
Version First Reported In: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: imaging-bugs-null
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-11-26 01:21 UTC by renner0
Modified: 2026-05-09 14:13 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/306489/events/d1331767f3e949488ae9d866465bb691/


Attachments
New crash information added by DrKonqi (225.08 KB, text/plain)
2025-11-26 01:21 UTC, renner0
Details

Note You need to log in before you can comment on or make changes to this bug.
Description renner0 2025-11-26 01:21:18 UTC
Application: plasmashell (6.5.3)

ApplicationNotResponding [ANR]: false
Qt Version: 6.10.1
Frameworks Version: 6.20.0
Operating System: Linux 6.17.8-300.fc43.x86_64 x86_64
Windowing System: Wayland
Distribution: Aurora (Version: latest-43.20251125.1)
DrKonqi: 6.5.3 [CoredumpBackend]

-- Information about the crash:
1. Right click your desktop
2. Click Desktop and Wallpaper

I sadly can't reproduce this anymore and this was just a one time thing.
If it helps I have avif and jxl images.
Feel free to close if this is just an issue with exiv2 and not how it is being called by libkexiv2(?)

ADDITIONAL INFORMATION

RX 6750XT

exiv2 0.28.6

The crash does not seem to be reproducible.

-- Backtrace (Reduced):
#7  0x00007f27b44e5d4b in XMPMeta::RegisterNamespace(char const*, char const*) () from /lib64/libexiv2.so.28
#8  0x00007f27b443390c in Exiv2::XmpParser::initialize(void (*)(void*, bool), void*) () from /lib64/libexiv2.so.28
#9  0x00007f27b443a9f9 in Exiv2::XmpParser::decode(Exiv2::XmpData&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () from /lib64/libexiv2.so.28
#10 0x00007f27b43c434c in Exiv2::BmffImage::parseXmp(unsigned long, unsigned long) () from /lib64/libexiv2.so.28
#11 0x00007f27b43c5620 in Exiv2::BmffImage::boxHandler(std::basic_ostream<char, std::char_traits<char> >&, Exiv2::PrintStructureOption, unsigned long, unsigned long) () from /lib64/libexiv2.so.28
#12 0x00007f27b43c6ab3 in Exiv2::BmffImage::readMetadata() () from /lib64/libexiv2.so.28
#13 0x00007f27b465b4b3 in KExiv2Iface::KExiv2::load(QString const&) const () from /lib64/libKExiv2Qt6.so.0
#14 0x00007f27b465cfa9 in KExiv2Iface::KExiv2::KExiv2(QString const&) () from /lib64/libKExiv2Qt6.so.0
#15 0x00007f27b46f3fb4 in MediaMetadataFinder::run() () from /usr/lib64/qt6/qml/org/kde/plasma/wallpapers/image/libplasma_wallpaper_image.so
#16 0x00007f27ec626a68 in QThreadPoolThread::run() () from /lib64/libQt6Core.so.6
#17 0x00007f27ec6c89ae in QThreadPrivate::start(void*) () from /lib64/libQt6Core.so.6
[...]
#7  0x00007f27b44e5d4b in XMPMeta::RegisterNamespace(char const*, char const*) () from /lib64/libexiv2.so.28
#8  0x00007f27b443390c in Exiv2::XmpParser::initialize(void (*)(void*, bool), void*) () from /lib64/libexiv2.so.28
#9  0x00007f27b443a9f9 in Exiv2::XmpParser::decode(Exiv2::XmpData&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () from /lib64/libexiv2.so.28
#10 0x00007f27b43c434c in Exiv2::BmffImage::parseXmp(unsigned long, unsigned long) () from /lib64/libexiv2.so.28
#11 0x00007f27b43c5620 in Exiv2::BmffImage::boxHandler(std::basic_ostream<char, std::char_traits<char> >&, Exiv2::PrintStructureOption, unsigned long, unsigned long) () from /lib64/libexiv2.so.28


Reported using DrKonqi
Comment 1 renner0 2025-11-26 01:21:20 UTC
Created attachment 187179 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Méven Car 2026-03-18 10:47:31 UTC
Definitely an upstream issue.
Please relay this to exiv2, https://github.com/exiv2/exiv2

If you could isolate/find the file triggering the crash and share it that would be very helpful.
Comment 3 renner0 2026-03-18 17:00:20 UTC
(In reply to Méven Car from comment #2)
> Definitely an upstream issue.
> Please relay this to exiv2, https://github.com/exiv2/exiv2
> 
> If you could isolate/find the file triggering the crash and share it that
> would be very helpful.

I have sadly not seen this bug since :(
Comment 4 renner0 2026-03-18 17:19:24 UTC
Is this snippet still worth reporting to them? With no other useful information?
Comment 5 Méven 2026-05-09 14:13:54 UTC
(In reply to renner0 from comment #4)
> Is this snippet still worth reporting to them? With no other useful
> information?

See their github template, and copy the crash trace and provide the file concerned ideally.