https://bugs.kde.org/show_bug.cgi?id=484463
--- Comment #3 from tagwer...@innerjoin.org --- That sounds like debugging output (stderr) from the process started by balooctl, that comes asynchronously to the console if you start baloo_file with a "balooctl enable" and of course it's not listening to any of your controls. I eventually had success making ensure stderr goes to the journal, https://bugs.kde.org/show_bug.cgi?id=460390#c2. What's needed is that a "balooctl enable" does a "systemctl --user start kde-baloo" (rather than launch baloo_file itself) -- You are receiving this mail because: You are watching all bug changes.
