https://bugs.kde.org/show_bug.cgi?id=437019
--- Comment #10 from tagwer...@innerjoin.org --- (In reply to David Kredba from comment #9) > Can someone reproduce it please? > Moving existing files indexed already to another folder and log off/on KDE > session is sufficient for me. I'm afraid I can only offer hints and suggestions from my experience... If you run balooshow for the files before/after a relogon, they have the same devicenumber/inode as per "stat" (and the correct filename as given in the square brackets)? At times, I have seen baloo "recognise" a new/changed file but, because of inode reuse (with Ext4), it still has "earlier" data in the index. Bug 435434. Baloo recognises the mismatch after a relogon (and you see "renaming" reports in the logs). In this case "balooctl monitor" did not show the file being indexed before the relogon. If I meet it again, I'll check the "balooctl status". You are not using hard/soft links anywhere? Anything that might confuse baloo's 'one to one' inode to filename ideal? If you purge and reindex, do you see the same behaviour if you reindex just a subset of your disk? > Last indexing try I speeded up using a symlink of .local/share/baloo folder > to a SSD drive. When done I moved it back. It's a good trick :-) Wishing you good luck... -- You are receiving this mail because: You are watching all bug changes.
