https://bugs.kde.org/show_bug.cgi?id=375131
ramos.kie...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ramos.kie...@gmail.com
--- Comment #2 from ramos.kie...@gmail.com ---
I have also experienced this behavior where baloo hangs forever on the same
file. The index remains at same file and doesn't finish indexing. The file
which baloo is stuck on can be found in kinfocenter under File Index Monitor.
Unlike Aqa-Ib though when baloo is stuck it didn't consume any CPU resources.
Baloo would get stuck on the same file even after deleting the index by issuing
`baloo disable` and `baloo enable`.
As a workaround I have had to delete the offending file and stop and restart
baloo usually with `balooctl stop` followed by `killall baloo_file`, `killall
baloo_file_extractor` and `balooctl start`.
I have had baloo get stuck on a PDF and on two different JPGs.
--
You are receiving this mail because:
You are watching all bug changes.
