¡Hola Leos! El 2017-11-14 a las 14:54 -0500, Leos Pohl escribió:
Package: baloo Version: 4:5.28.0-2 Severity: important
When baloo indexes files, it takes up all system resources (CPU, memory, disk) and the computer becomes unusable until it finishes which can take from several minutes to almost half an hour. This is erroneous behavious as it equals crashing the system. There need to be implemented limitations that baloo has to respect to provide a usable indexing. Also the indexing runs not only when the computer is idle but also under load. When I get the console running and ask balooctl status, I after almost a minute: Baloo File Indexer is running Indexer state: Idle Indexed 34283 / 34283 files Current size of index is 15.80 GiB
How can it be idle when even the terminal is unusable...
Please maintainer, is there any fix that could be applied to stable debian that resolves this issue?
In Debian, the baloo file indexer is disabled by default. As the current baloo implementation doesn't scale nicely, (or at all in 32bit systems).
Please consider disabling it or following the issues with the baloo file indexer with the upstream developers, as it's infeasible to fix it from the Debian side.
Happy hacking, -- "Don't let what you cannot do interfere with what you can do." -- Wooden's Rule Saludos /\/\ /\ >< `/
signature.asc
Description: PGP signature
