Summary: | Immediate Crash upon Bootup | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kfilemetadata | Reporter: | Armando <armandogarciasf> |
Component: | general | Assignee: | Pinak Ahuja <pinak.ahuja> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | nate |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.55.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Armando
2019-02-15 22:47:03 UTC
Crashing in KFileMetaData::TagLibExtractor::extract(). Do you by any chance have any .spx files and/or can you pinpoint the file that causes the crash by using `balooctl monitor`? (In reply to Nate Graham from comment #1) > Crashing in KFileMetaData::TagLibExtractor::extract(). > > Do you by any chance have any .spx files and/or can you pinpoint the file > that causes the crash by using `balooctl monitor`? Thank you for responding. I am unfamiliar with Baloo or its role on my system, but I do have some .spx files on my system (packaged into .gdb files). These files are associated with ESRI ArcMaps. Running 'balooctl monitor' indicates that it has indexed one of the .spx files: :~$ balooctl monitor Press ctrl+c to stop monitoring File indexer is running Indexing file content Indexing: /home/[folder]/Documents/Records/Academic/Coursework/[folder]/Final/Shapefiles 2/[private]/Census_Income_Tracts.gdb/a00000004.spx Thank you, I'll await any further questions or instructions. Yep, that's what I suspected. We're already tracking the fix in Bug 403902. Baloo should stop crashing in KDE Frameworks 5.56 because we disabled indexing .spx files. We're still looking into how to resolve the crash itself (which is why the duped bug is still open) *** This bug has been marked as a duplicate of bug 403902 *** |