https://bugs.kde.org/show_bug.cgi?id=453278
Bug ID: 453278
Summary: Baloo doesn't reindex files after they have been moved
or renamed - manually reindexing is necessary...
Product: frameworks-baloo
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: piedro.kul...@gmail.com
Target Milestone: ---
SUMMARY
on my system baloo only searches the documents and music folder. Tagging,
content and file name search works initially. But when I work with the files -
renaming them, moving some in subfolders or renaming the containing folder
they disappear from the index.
STEPS TO REPRODUCE
1. index a file in a subfolder in Documents ("recent_path", "recent_file_name")
2. rename the subfolder or the file or both ("current_path",
"current_file_name")
3. search for the content or the file name of the current file in the current
folder
OBSERVED RESULT
Absurd: the search can't find the file name nor the content of the file in the
current folder - though it is right there in the dolphin window if you do not
search for it (navigate > current folder > content: this one current file!)
EXPECTED RESULT
To find the only file in the current folder by it's name within the current
folder...
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch linux 5.17.5-arch1-1, fully updated
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
the current file's index can be shown with
"balooshow -x /current_path/current_file_name"
but the file index information output still contains the old file path
"/recent_path/recent_file_name"!
So my guess is that after renaming a file the index isn't updated - baloo
sleeps on the job. It doesn't matter to wait a while or reboot - only
reindexing does the job to update the files index information to include the
correct path and file name.
On a curious note: Is it normal that some tags are shown as "TAG-tagname1" and
others as "TAtagname2" or is this a hint that something with the indexing
isn't right anyway?
--
You are receiving this mail because:
You are watching all bug changes.
