https://bugs.kde.org/show_bug.cgi?id=392793
--- Comment #3 from tagwer...@innerjoin.org ---
Recognise this from Fedora 32, indexing is working but then 'stops' at some
point. A "balooctl check" triggers a reindex and there is a scurry to catch up
with the files that need reindexing.
I can reproduce when renaming a parent folder
In Neon testing (Plasma 5.20.3, Frameworks 5.77, Qt 5.15.1, Filesystem Ext4,
New install)
balooctl purge
cd Documents
mkdir folder1
echo "Test File" > folder1/filea.txt
baloosearch Test
gives what is should:
/home/bug392793/Documents/folder1/filea.txt
If you rename the folder:
mv folder1 folder2
this pops up an error (nicely visible if you have previously done a "balooctl
purge")
replace called with invalid arguments, docId: 7330929353751553 url:
"/home/bug392793/Documents/folder2/"
and
baloosearch Test
shows the "old results" (*):
/home/bug392793/Documents/folder1/filea.txt
It has not seen the change. If you nudge baloo check:
balooctl check
You get:
replace called with invalid arguments, docId: 5647955008748545 url:
"/home/bug392793/"
7330929353751553 "/home/bug392793/Documents/folder2" renaming "folder1" to
"folder2"
Started search for unindexed files
and it updates/corrects the index. A search:
baloosearch Test
then gives the correct results:
/home/bug392793/Documents/folder2/filea.txt
It is noticeable that if you have renamed a folder (as per the "*" above), you
can create/write/change all sorts files in the newly renamed folder without
these being indexed
Installed inotify-tools and ran inotifywait in a separate shell:
inotifywait -mr Documents/
iNotify saw the folder rename:
Documents/ MOVED_FROM,ISDIR folder1
Documents/ MOVED_TO,ISDIR folder2
Documents/folder2/ MOVE_SELF
--
You are receiving this mail because:
You are watching all bug changes.
