https://bugs.kde.org/show_bug.cgi?id=438455
--- Comment #27 from tagwer...@innerjoin.org --- (In reply to Guido from comment #25) > (In reply to tagwerk19 from comment #24) > I tried your suggestion, rebooted, stopped baloo, purged, reenabled but I > have nothing in journald about indexing, only the message tha baloo is > starting I'll admit I've not fully understood how to get baloo to output debug messages. My experience so far if that, having set up the qtlogging.ini file, and I do a 'balooctl purge' on a console, I get to see the warning/debug messages streamed to that console. I have recently found that if I redirect the stderr to /dev/null - with a 'balooctl purge 2> /dev/null' I see the messages in the journal. I would love to know how properly to control this (Bug 460390) -- You are receiving this mail because: You are watching all bug changes.
