Jaroslav Reznik wrote:
So it's kWarning, not kDebug and it can't be ignored by using
kdebugdialog
settings. There are two options - fix the underlying issue or change
kWarning to kDebug - it just depends on how important it is and it seem
as Harald already pointed out - nobody really cares. I found one another
example of mimetypes kWarning being changed just to kDebug. But I'm not
skilled in mimetypes at all :).
Maybe we should just silence everything less than qFatal by default?
Kevin Kofler