https://bugs.kde.org/show_bug.cgi?id=500595
Stefan Brüns <stefan.bru...@rwth-aachen.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stefan.bruens@rwth-aachen.d
| |e
Resolution|--- |WAITINGFORINFO
Status|REPORTED |RESOLVED
--- Comment #1 from Stefan Brüns <stefan.bru...@rwth-aachen.de> ---
Unfortunately, lmdb crashes if it encounters an error, instead of giving the
caller any feedback (return code denoting failure).
If such an error (crash) happens in the content indexer, baloo will handle it,
but when this happens in the daemon (baloo_file) itself, the problem will
reappear.
Currently, you have to solve this manually by running "balooctl6 purge".
--
You are receiving this mail because:
You are watching all bug changes.
