Package: baloo Version: 4:5.28.0-2 Severity: important Dear Maintainer,
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? -- System Information: Debian Release: 9.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages baloo depends on: ii baloo-kf5 5.28.0-2 baloo recommends no packages. baloo suggests no packages. -- no debconf information