Summary: | Baloo File Extractor crashes everytime on boot in KFileMetaData::PopplerExtractor::extract | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kfilemetadata | Reporter: | aawasthi |
Component: | general | Assignee: | Pinak Ahuja <pinak.ahuja> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | CC: | nate, tagwerk19 |
Priority: | NOR | Keywords: | drkonqi |
Version First Reported In: | 5.105.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
aawasthi
2023-08-06 07:21:20 UTC
Looks like the issue is in KFileMetaData or poppler, which is crashing while trying to parse a document for content indexing. Any chance you can attach the PDF file causing this crash? You can find it by running `balooctl failed` in a terminal window? Obviously if the document contains sensitive atomic secrets, don't attach it. :) But then it will probably be difficult or impossible to fix the issue, unfortunately. (In reply to Nate Graham from comment #1) > Looks like the issue is in KFileMetaData or poppler, which is crashing while > trying to parse a document for content indexing. Any chance you can attach > the PDF file causing this crash? You can find it by running `balooctl > failed` in a terminal window? > > Obviously if the document contains sensitive atomic secrets, don't attach > it. :) But then it will probably be difficult or impossible to fix the > issue, unfortunately. Thank you for your efforts. However, "balooctl failed" returns "All Files were indexed successfully". Hmm, thanks anyway. The bug has disappeared on reinstalling "Poppler" package, which provides "libpoppler.so.123". Cool, I guess it was a local installation or configuration issue. (In reply to Nate Graham from comment #5) > Cool, I guess it was a local installation or configuration issue. Looks like. Thank you and team for all your efforts. |