[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 Nate Graham changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #15 from Nate Graham ---

[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 --- Comment #14 from skierpage --- (In reply to Alexander Stippich from comment #12) > Please re-check with KF 5.58, another fix was added for the exivextractor > there Good news, Fedora 30 KDE spin updated to KDE Frameworks 5.58.0, and

[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 --- Comment #12 from Alexander Stippich --- Please re-check with KF 5.58, another fix was added for the exivextractor there -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 skierpage changed: What|Removed |Added Status|NEEDSINFO |REOPENED Ever confirmed|0

[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 --- Comment #10 from skierpage --- (In reply to Craig Denman from comment #6) > I cannot figure out how to find the offending file. I filed bug 405247 requesting some way to get baloo_file_extractor to report the problem file. In a terminal

[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 Alexander Stippich changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 --- Comment #8 from Alexander Stippich --- KDE Frameworks 5.56 contains a change that may also fix your crash. Can you retest? -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 --- Comment #7 from Alexander Stippich --- You should be able to find the file when you type "balooctl monitor" in a console. It shows files that are currently indexed by baloo. If there is a crash somewhere, baloo monitor is usually stuck and shows

[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 --- Comment #6 from Craig Denman --- I cannot figure out how to find the offending file. In the referenced bug report 40517 I see that I can use: Balooctl Status Is there a way to do something like a recursive scan to find the error.  I am

[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 Nate Graham changed: What|Removed |Added CC||skierp...@gmail.com --- Comment #5 from Nate

[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 --- Comment #4 from Nate Graham --- A file that causes this crash can be found in the comment on this duped bug: https://bugs.kde.org/show_bug.cgi?id=405017#c4 -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file

https://bugs.kde.org/show_bug.cgi?id=404565 Nate Graham changed: What|Removed |Added Summary|baloo_file_extractor|baloo_file_extractor |crashes