Dne neděle 20. března 2016 12:45:00 CET, John Andersen napsal(a):
On 03/20/2016 03:12 AM, Vojtěch Zeisek wrote:
If You are on KDE4/5 and You have Baloo running, turn it off temporally (balooctl stop; kilall -SIGTERM baloo_file; killall -SIGTERM baloo_file_extractor) or forever (balooctl disable). Or suffer and let it run overnight until the indexing is done. It can cause huge I/O and cause other applications to hang terribly. When files are indexed, it is not that terrible. This is nonsense. Baloo hasn't acted that way in a couple years. It is "nice"-ed very well, it only indexes your home directory, and eve a large home directory will index without any inconvenience to the user.
Don't paint Baloo with Nepomuk's paintbrush.
I wasn't exact. But I must disagree. I meant initial indexing. Might be I have too much weird data, but the initial indexing is a pain. I was always pain on KDE 4. When this is done, it runs nicely. I wasn't able to reach this phase yet on KDE 5... -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/