There is a fix for this in upstream. The svn commit is linked to in the upstream bug report. Can we get a patch with this for kde 4.4.5? It's a really bad bug.
There are still other kde apps that spam. kdebugdialog does not seem to have any effect, even with "disable all debug output". I have compiled the standard kde 4.5.2 packages with -debug. Is debug $USES perhaps getting set anyways somehow during build? (eix still reports -debug).
(In reply to comment #0) > There is a fix for this in upstream. The svn commit is linked to in the > upstream bug report. > > Can we get a patch with this for kde 4.4.5? It's a really bad bug. > I've added this patch in kdelibs-4.4.5-r2. Please test! (In reply to comment #1) > There are still other kde apps that spam. kdebugdialog does not seem to have > any effect, even with "disable all debug output". > I have compiled the standard kde 4.5.2 packages with -debug. Is debug $USES > perhaps getting set anyways somehow during build? (eix still reports -debug). > Should not... this is what kde does in every new version again. Filing a new bug upstream is probably best...
(In reply to comment #2) > I've added this patch in kdelibs-4.4.5-r2. Please test! Well, for KDE 4.4.9 the version -r2 results still in : tfoerste@n22 ~ $ konqueror https://bugs.kde.org/query.cgi QPainter::begin: Widget painting can only begin as a result of a paintEvent QPainter::translate: Painter not active QPainter::setClipRect: Painter not active QPainter::hasClipping: Painter not active QPainter::setPen: Painter not active ...