Bug 514150 - baloo_file does not quit when baloo is disabled
Summary: baloo_file does not quit when baloo is disabled
Status: REPORTED
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: balooctl (other bugs)
Version First Reported In: 6.21.0
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-04 17:09 UTC by Richard Day
Modified: 2026-01-05 00:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Day 2026-01-04 17:09:11 UTC
SUMMARY

After running `balooctl6 disable` `baloo_file` continues to run for at least 10 minutes consuming CPU and I/O resources.

STEPS TO REPRODUCE
1. Ensure `baloo` is enabled
2. Create/modify files so that baloo starts to scan them
3. Execute `balooctl6 disable`
4. Note how `baloo_file` continues to run, ignoring disable request

OBSERVED RESULT

Increased CPU usage, increased CPU temperature, increased I/O temperature, possible CPU throttling, increased laptop battery drain

NOTE: `baloo_file` does NOT quit or reduce CPU usage when laptop power supply is removed where, even when enabled, baloo should idle itself.
 
EXPECTED RESULT

`baloo_file` should stop when baloo is disabled.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.18.2-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 16 × 12th Gen Intel® Core™ i7-1260P
Memory: 16 GiB of RAM (15.3 GiB usable)
Graphics Processor: Intel® Iris® Xe Graphics
Manufacturer: LENOVO
Product Name: 21CD005DUK
System Version: ThinkPad X1 Yoga Gen 7
Comment 1 tagwerk19 2026-01-05 00:29:08 UTC
Without bashing this to see exactly what's happening, I think a disable is queued, it might take a while to take effect...