https://bugs.kde.org/show_bug.cgi?id=493520
--- Comment #5 from tagwer...@innerjoin.org --- (In reply to Randall Larson from comment #3) > $ ls -lh .local/share/baloo/index > -rw-r--r-- 1 <USER> <GROUP> 2.6M Sep 22 22:45 .local/share/baloo/index > > I am using btrfs, but the index file does not seem _that_ big .... No, that's not big. You should start worrying when it gets as big as your available RAM (as a very, very approximate measure) > ... I've noticed this crash > happens when its in the process of attempting to index files on my fusemount > (rclone to MS OneDrive). Right now, it does seem to be "hung" when trying > to index a photo of type .heic. For the short term, I will disable indexing > of my fusemount, but is it _expected_ that it hang on .heic files? Well, you can try copying the .heic to a non-fusemounted folder or you can get a test sample. I tend to go to https://filesamples.com/ You can try doing the indexing in the foreground, with: $ balooctl index sample1.heic and check what's been extracted with $ balooshow -x sample1.heic (Possibly with balooctl6 and balooshow6 rather than balooctl and balooshow) I'm still a little suspicious that it is baloo_file failing and not baloo_file_extractor. If there was an issue reading or extracting the metadata, it would be the extractor crashing... -- You are receiving this mail because: You are watching all bug changes.
