[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor

2020-11-05 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405017 --- Comment #10 from Nate Graham --- *** This bug has been marked as a duplicate of bug 405210 *** -- You are receiving this mail because: You are watching all bug changes.

[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor

2019-05-26 Thread skierpage
https://bugs.kde.org/show_bug.cgi?id=405017 --- Comment #9 from skierpage --- KDE Frameworks 5.58.0 seems to have fixed the crash \o/ -- You are receiving this mail because: You are watching all bug changes.

[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor

2019-05-13 Thread skierpage
https://bugs.kde.org/show_bug.cgi?id=405017 --- Comment #8 from skierpage --- (In reply to Alexander Stippich from comment #7) > This should be fixed by > https://phabricator.kde.org/R286:6e449d44bb5dd7aca58464306d0b7da1312be8ee > which was included in KF 5.56 Sadly I still get a crash with KDE

[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor

2019-03-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405017 Nate Graham changed: What|Removed |Added Latest Commit||https://phabricator.kde.org |

[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor

2019-03-17 Thread Alexander Stippich
https://bugs.kde.org/show_bug.cgi?id=405017 Alexander Stippich changed: What|Removed |Added CC||a.stipp...@gmx.net --- Comment #7 from Ale

[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor

2019-03-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405017 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED

[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor

2019-03-11 Thread skierpage
https://bugs.kde.org/show_bug.cgi?id=405017 --- Comment #5 from skierpage --- Created attachment 118727 --> https://bugs.kde.org/attachment.cgi?id=118727&action=edit New crash information added by DrKonqi baloo_file_extractor (5.55.0) using Qt 5.11.3 - What I was doing when the application cr

[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor

2019-03-09 Thread skierpage
https://bugs.kde.org/show_bug.cgi?id=405017 skierpage changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0

[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor

2019-03-08 Thread skierpage
https://bugs.kde.org/show_bug.cgi?id=405017 skierpage changed: What|Removed |Added CC||skierp...@gmail.com -- You are receiving this mail

[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor

2019-03-08 Thread skierpage
https://bugs.kde.org/show_bug.cgi?id=405017 --- Comment #2 from skierpage --- (In reply to Nate Graham from comment #1) > You can run `balooctl status` to see which file it crashes on. That didn't help, it just prints the status of the index. Instead I moved all the pictures to (unindexed) /tmp,

[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor

2019-03-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405017 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC|