Package: libqt5core5a
Version: 5.9.0~beta+dfsg-1
Severity: important
As a fix for bug 805399, the file /etc/xdg/QtProject/qtlogging.ini was added to
disable debug output from Qt (using *.debug = false).
This fix breaks the developer experience, because it makes qDebug() do nothing
when working on a Qt application.
The way it's supposed to work is that KDE apps and libs are supposed to be
using categorized logging (qCDebug, qCWarning etc.), with severity "debug"
being disabled by default.
This way, the default category, the one used by qDebug(), should keep working.
Bug 805399 shows for instance this line:
org.kde.kded5[4940]: org.kde.kurifilter-shorturi: path = "xterm"
isLocalFullPath= false exists= false url= QUrl("xterm")
This comes from KIO (which I maintain). Investigation shows this one has been
fixed : since KDE Frameworks 5.23, the logging category is defined as
QLoggingCategory category("org.kde.kurifilter-shorturi", QtWarningMsg);
which means warnings (and above) are enabled by default, but debug is disabled
by default.
The debug messages from kioremote don't exist anymore since commit 2a3b74df
in plasma-workspace (the code has now moved to kio).
So, overall, I think the underlying issue is fixed, we're trying to be better
citizens by using qCDebug and by disabling debug output for all specific
categories (since Qt 5.4 which supports it).
Conclusion: please remove /etc/xdg/QtProject/qtlogging.ini again.
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5
