https://bugs.kde.org/show_bug.cgi?id=516872
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from [email protected] --- First off, try without indexing hidden files/folders and see if the behaviour persists... There can be a lot happening, for example under .cache, that give Baloo a lot to do. Second option, have a look at the test here: https://bugs.kde.org/show_bug.cgi?id=402154#c12 Baloo depends on a stable File System ID for the disk (previously it used the device number which for some filesystems was *not* stable across reboots) and a inodes. If it sees a file "reappear" with a different FSID/inode it reindexes it... See what "stat" for a file shows, reboot and recheck. Earlier in the Bug 402154 thread, it's said that ZFS is not supported, checking with "stat" would give a potential explanation... You can also do a baloosearch6 of an indexed file, ideally you should get a single hit. If the FSID/inode of the source file changes on reboot, and the file is reindexed, you could get several hits. Finally, maybe restrict the indexing to a single test folder while troubleshooting and see if there might be any connection with Cyrillic filenames, I have no experience here. -- You are receiving this mail because: You are watching all bug changes.
