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

--- Comment #3 from Laurent Montel <mon...@kde.org> ---
(In reply to Stefan Brüns from comment #2)
> (In reply to Laurent Montel from comment #1)
> > "As can be seen from the output of
> > https://lxr.kde.org/search?_filestring=frameworks&_string=Q_LOGGING_CATEGORY
> > 
> > the default log level for different debug categories varies from
> > QtCriticalMsg to QtInfoMsg."
> > 
> > all module which doesn't use debug categories files will not override by
> > kdebugsettings => so kdebugsettings will not change settings for these
> > modules.
> > 
> > But indeed it will change settings for other modules.
> > 
> > But default all module uses same settings generated by categories ecm macro.
> > 
> > => QtInfoMsg
> > 
> > see  #if QT_VERSION >= QT_VERSION_CHECK(5, 4, 0)
> > Q_LOGGING_CATEGORY(RUQOLA_DDPAPI_COMMAND_LOG,
> > "org.kde.ruqola.ddpapi.command", QtInfoMsg)
> > #else
> > Q_LOGGING_CATEGORY(RUQOLA_DDPAPI_COMMAND_LOG,
> > "org.kde.ruqola.ddpapi.command")
> > #endif
> > 
> > "
> > => it's normal. 
> 
> grep kf5.kio.kio_http  /etc/xdg/*categories
> /etc/xdg/kde.categories:kf5.kio.kio_http KIO HTTP slave (KIO)
> 
> https://lxr.kde.org/source/frameworks/kio/src/ioslaves/http/http.cpp#0080
> 0080 Q_LOGGING_CATEGORY(KIO_HTTP, "kf5.kio.kio_http", QtWarningMsg) //
> disable debug by default

So it's a bug in this package.
We must create a categories file if we don't use generated categories file
otherwise it's impossible to which type of warning is setting.



> 
> > "
> > 3. Setting the log level to QtInfoMsg increases the log level for every
> > category which defaults to Critical or Warning"
> > 
> > it's wrong as we can't change settings from module which doesn't use debug
> > categories file.
> 
> See above - even modules with categories file have deviating settings.

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

Reply via email to