https://bugs.kde.org/show_bug.cgi?id=435119
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #8 from tagwer...@innerjoin.org ---
(In reply to Mina from comment #6)
> ... I used "~/Documents/TestBaloo" instead, because my Documents
> folder is quite messy ...
The only reason I suggested "Documents" is that not all distributions index all
folders. As far as I can tell, everyone indexes "Documents" :-)
> $ balooctl status
>
> It stays blank and I have to hit Ctrl + C to exit.
Never met that! Doesn't sound healthy :-/
> $ balooctl purge
> Stopping the File Indexer ............................
>
> Not sure if you can see the output correctly, but it's just lots of dots and
> "failed to stop" in the end.
Have met that. More in the past, maybe less so recently...
My gut feeling is the baloo index has got corrupted. It happens and in that
case the best option is to start again from scratch.
If you cannot do a "balooctl purge", do a "balooctl disable" (which might still
fail to stop) and reboot. The "disable" should prevent baloo starting up again
when you log back in.
You should then be able to run a "balooctl monitor" in one window, a "balooctl
purge" to delete the index and then a "balooctl enable" to start the indexing
in a second window (it may be that you need a "balooctl enable" followed by a
"balooctl enable" as it sometimes needs to be told twice)
If you have no luck with "balooctl purge", the index file lives at:
.local/share/baloo/index
and you can stop baloo and delete it manually.
> ... Yeah my neon is with me since 18.04 and I upgraded it to 20.04
There's a Bug 431664 about needing to reindex if you had been running a baloo
5.68 or earlier
> Hope any of this makes sense.
Thank you, yes :-)
--
You are receiving this mail because:
You are watching all bug changes.
