https://bugs.kde.org/show_bug.cgi?id=510149

--- Comment #7 from Stefan Brüns <[email protected]> ---
(In reply to TraceyC from comment #5)
> (In reply to tagwerk19 from comment #4)
> > I suspect you have a
> >     ~/.config/QtProject/qtlogging.ini
> > file containing something like:
> >     [rules]
> >     ...
> >     kf.baloo.*=true
> >     ...
> > in it.
> 
> That file is on the system, but doesn't have that line. That's fine, at this
> point the developers should have enough information to investigate further.

There is also a graphical tool to edit debug levels for each category (i.e.
application/library/implementation detail/...). If you hover the mouse cursor
over an entry, it will tell you the corresponding category name (e.g "Baloo
Engine" - Category name: kf.baloo.engine).

These setting will affect the whole session, and may fill your user session
logfile (journal) with a large amount of messages. For debugging, just set the
corresponding environment variable:

$> QT_LOGGING_RULES='kf.baloo.*=true;*.debug=false' baloosearch6 \"simnh
blinm\"

Note, you can supply multiple rules, the rule above enables full logging for
all baloo components, but then disables all debug messages (i.e. only keeping
warning/informational messages).

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to