https://bugs.kde.org/show_bug.cgi?id=474973
--- Comment #4 from tagwer...@innerjoin.org ---
(In reply to John Kizer from comment #3)
> Hi - Does the attachment I just added show what might be helpful in this case?
Snip...
> $ baloosearch -d /home/johnkizer/Documents/ Erika-9th
> Elapsed: 0.316861 msecs
>
> $ baloosearch Erika-9th
> /home/johnkizer/Documents/Erika-9th-birthday-planning-2023.ods
> /home/johnkizer/Documents/Erika-9th-birthday-planning-2023.ods
> /home/johnkizer/Documents/Erika-9th-birthday-planning-2023.ods
> /home/johnkizer/Documents/Erika-9th-birthday-planning-2023.ods
> /home/johnkizer/Documents/Erika-9th-birthday-planning-2023.ods
See what
$ baloosearch -i Erika-9th
gives you...
The "-i" tells baloosearch to include the ID it has for the file in its index.
This is based on the minor device number (more or less) and inode. What you are
seeing is typical for openSUSE (that uses BTRFS intensively) and, up until
recently, Fedora. The problem is that you can get a different minor device
number each reboot and baloo will reindex the file each time - my guess is that
you'll see each "hit" given with a different ID.
I've not seen this issue affect the issue affecting "baloosearch -d" filtering,
but it anything is possible.
There's a patch coming for this with Frameworks 5.111, middle of this month:
https://bugs.kde.org/show_bug.cgi?id=402154#c62
After the patch it would be sensible to clear and rebuild the index (with a
"balooctl purge" and some patience). You don't have to but it would clear out
all the old records which is probably good in your case.
--
You are receiving this mail because:
You are watching all bug changes.
