https://bugs.kde.org/show_bug.cgi?id=435802
Bug ID: 435802
Summary: Baloo does not index a recreated folder
Product: frameworks-baloo
Version: 5.81.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: stefan.bru...@rwth-aachen.de
Reporter: tagwer...@innerjoin.org
CC: baloo-bugs-n...@kde.org, n...@kde.org
Target Milestone: ---
SUMMARY
If baloo is told to index a folder, it doesn't notice changes when
the folder is deleted and recreated if the parent folder is not monitored.
STEPS TO REPRODUCE:
Restrict indexing to one folder ~/Testdir, in .config/baloofilerc:
exclude folders[$e]=$HOME/
folders[$e]=$HOME/Testdir/
Run
balooctl monitor
in one window. Remove the folder
rm -r ~/Testdir
and purge the index in a second:
balooctl purge
Create the folder and a testfile:
mkdir ~/Testdir
echo "This is a testfile" > ~/Testdir/testfile.txt
OBSERVED RESULTS
Baloo does not see the folder being created (or the testfile being
created in it)
Needs a "balooctl check" before indexing testfile.txt
EXPECTED RESULTS
Baloo should explicitly keep watch on folders mentioned in the
"include" list.
If the parent folder is watched, then changes would be picked up
by iNotify. If the parent folder is not watched, an explicit check
is most likely needed.
SOFTWARE/OS VERSIONS
Neon Testing
Baloo : 5.81.0
Plasma : 5.21.3
Frameworks : 5.81.0
Qt : 5.15.2
ADDITIONAL INFORMATION
Admittedly a messy, maybe unusual, edge case...
--
You are receiving this mail because:
You are watching all bug changes.
