On 01/02/2016 08:49 AM, stakanov@freenet.de wrote:
Your system is running baloo file indexing on the whole disk. The delays will be in the same moment as heavy disk activity I suppose. Once the indexing process has finished, the system will turn to be normally responsive. Log in your user and just let it run. Go to bed and when you wake up it should be O.K. This has normally nothing to do with conflicts. Try "top" from the command line to see that balloo indexer is running requiring a lot of CPU load.
Is there a way to tell when baloo file indexing is complete, besides top? Is there a command line tool or something that you can type in that will say it is 90% or 100% or anything like that? -- George Box #1: 13.2 | KDE 4.14 | AMD Phenom IIX4 | 64 | 16GB Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org