https://bugs.kde.org/show_bug.cgi?id=405017
Bug ID: 405017
Summary: baloo_file_extractor crash, in
Exiv2::DataValue::toLong in
kfilemetadata_exiv2extractor
Product: frameworks-baloo
Version: 5.54.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: skierp...@gmail.com
Target Milestone: ---
SUMMARY
I dragged some files from my camera onto my drive, and the Crash Reporting
Assistant popped up to report that baloo_file_extractor had crashed.
STEPS TO REPRODUCE
1. Drag a bunch of files from camera via MTP to indexed drive.
OBSERVED RESULT
Crash Reporting Assistant popped up. After installing debuginfo (and fixing
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Fedora
), the crash report indicates the crash is in kfilemetadata_exiv2extractor:
#6 0x00007f09a8cb253f in raise () from /lib64/libc.so.6
#7 0x00007f09a8c9c895 in abort () from /lib64/libc.so.6
#8 0x00007f0993dd6278 in std::__replacement_assert
(__file=__file@entry=0x7f0993eeff08 "/usr/include/c++/8/bits/stl_vector.h",
__line=__line@entry=950, __function=__function@entry=0x7f0993f4c740
<std::vector<unsigned char, std::allocator<unsigned char>
>::operator[](unsigned long) const::__PRETTY_FUNCTION__> "std::vector<_Tp,
_Alloc>::const_reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp,
_Alloc>::size_type) const [with _Tp = unsigned char; _Alloc =
std::allocator<unsigned char>; std::vector"...,
__condition=__condition@entry=0x7f0993eefed8 "__builtin_expect(__n <
this->size(), true)") at
/usr/include/c++/8/x86_64-redhat-linux/bits/c++config.h:2389
#9 0x00007f0993e8dc85 in std::vector<unsigned char, std::allocator<unsigned
char> >::operator[] (__n=<optimized out>, this=<optimized out>) at
/usr/src/debug/exiv2-0.26-12.fc29.x86_64/src/value.cpp:229
#10 Exiv2::DataValue::write (os=..., this=<optimized out>) at
/usr/src/debug/exiv2-0.26-12.fc29.x86_64/src/value.cpp:233
#11 0x00007f0993e8dcb9 in Exiv2::DataValue::toLong (this=<optimized out>,
n=<optimized out>) at /usr/include/c++/8/bits/stl_vector.h:948
#12 0x00007f0998615529 in ?? () from
/usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so
Unfortunately, the Baloo file indexing machinery gives no indication what file
it's working on when there's a crash.
EXPECTED RESULT
No crash
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
ADDITIONAL INFORMATION
I know the 59 files that I dragged in that seemed to trigger this crash. Is
there some way to run baloo_file_extractor on each, one by one? (I couldn't
find any documentation for this program.) If I run `balooctl index <filename>`
for each one, it mostly reports "Already scheduled for indexing".
--
You are receiving this mail because:
You are watching all bug changes.
