https://bugs.kde.org/show_bug.cgi?id=434796
--- Comment #6 from tagwer...@innerjoin.org ---
Things to think about...
It can take some seconds for baloo to see that a new file has appeared and then
index it. If you run 'balooctl monitor' in a separate window you can see the
file streaming past as they are indexed.
It's possible to kick baloo to look through 'all files' and catch up with any
it has missed. Keep the monitor running and run a 'balooctl check' in a new
window.
Baloo should see new files appear and files as they are updated. It uses
something called 'inotify'. It then decides whether to index the file or not,
depending on the folder (included or excluded directories) or file types. My
guess though, if you can find 'Fragen-Excel.xlsx' you would (normally) be able
to find a 'Fragen-Excel (1).xlsx' in the same folder.
You can explicitly tell baloo to index the file with
balooctl index filename
If 'balooshow -x' doesn't see the file after that, then there's something
different happening ...
... It may worth trying the test with a real .xlsx file (rather than a
'touched' empty one). Baloo is checking whether the .xlsx is 'zipped' and might
be confused as it's an empty file.
--
You are receiving this mail because:
You are watching all bug changes.
