https://bugs.kde.org/show_bug.cgi?id=420339
--- Comment #11 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #0)
> STEPS TO REPRODUCE:
>
> Create a file:
>
> touch ~/Pictures/image.jpg
>
> confirm that Baloo has indexed it:
>
> balooshow ~/Pictures/image.jpg
>
> baloosearch image.jpg
>
> Look for "image.jpg" in dolphin's search dialog and type "image.jpg"
With a little bit of experience from elsewhere...
https://bugs.kde.org/show_bug.cgi?id=457522#c17
If baloo is *not* content indexing then "kmimefiletype" and "balooshow -x" both
show image.jpg as image/jpeg, whereas if baloo is content indexing, "balooshow
-x" shows the mimetype as application/x-zerosize.
Debug output after a "balooctl purge":
kf.baloo: Indexing 5636161028553729 "/home/test/Pictures/image.jpg"
"application/x-zerosize"
kf.filemetadata: No extractor for "application/x-zerosize"
Seems to be a pretty solid behaviour. In this situation
baloosearch -i image.jpg
does find the file and
baloosearch -i -t image image.jpg
doesn't (and presumably krunner follows the baloosearch behaviour...)
--
You are receiving this mail because:
You are watching all bug changes.
