https://bugs.kde.org/show_bug.cgi?id=490928
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to robakjoshua from comment #0)
> Operating System: openSUSE Tumbleweed 20240726
Tumbleweed implies you are running with BTRFS? Or at least there's a strong
likelihood....
Simple stuff first, how big is your .local/shared/baloo/index file? and what
happens if you do a command line search for a file you know you've indexed?
$ baloosearch6 -i "one-of-your-files.txt"
The thing to watch for is if you get multiple results for the one file. The
"-i" is asking baloosearch to give you the internal DocID that Baloo has for
the file, OpenSUSE (with BTRFS) was caught by a bug in Baloo (or the way the
BTRFS subvolumes were mounted) in that with a reboot, the BTRFS disks were
mounted with different device numbers. Baloo saw a file with a different Device
Number (same inode but different device number) as a new file and reindexed it.
Multiple results are bad...
That was fixed spring last year and most systems should now have the patch. It
may be that you are running with a lot of old index data and have gradually
upgraded (on a rolling release) to the new system. It's probably best to purge
the old index and start afresh....
A possible reason why you are suddenly seeing issues is that you might have
deleted a large batch of files, Baloo needs to look through its "much expanded"
index and remove the references from the "indexed words" to the (multiple)
"indexed files". I seem to remember that process continues even if you've
switched to indexing just the filenames.
So...
Purge the index and start afresh...
Add folder exclusions for ".cache" and ".local/share/Trash", maybe ".mozilla"
if you have it, and also ".snapshots". Watch out specifically for the last. You
might not be snapshotting into your Home folder, but if you are, and Baloo is
indexing it, that's bad news!
See if you see files being indexed with "balooctl6 monitor"
Sorry, this is a hurried response before going offline for a couple of weeks
and contains guesswork. Should be able to reply again mid August...
--
You are receiving this mail because:
You are watching all bug changes.
