Bug 304833 – kde-4.4.1: .xsession-errors grows rampantly due to QPainter and many more debug messages

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Matt Whitlock 2010-02-13 09:04:12 UTC]

My .xsession-errors file is now almost 1 GB in size due to QPainter's frequently spitting out messages like the following:

QPainter::hasClipping: Painter not active
QPainter::setClipRegion: Painter not active
QPainter::setClipRegion: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active

Probably this is not a problem with QPainter itself but with something else that is misusing it.  That something else might be Konqueror.  If I follow the tail of .xsession-errors, I can see these log output lines filling it up by the screenful while I mouse over the text input components on this bug report page into which I'm currently typing this report.  Bunches of QPainter messages are spit out every time the cursor blinks and every time I press a key on the keyboard.

Here's how I have qt-gui and kdelibs installed:

$ emerge -ptv qt-gui kdelibs

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild   R   ] kde-base/kdelibs-4.4.0  USE="alsa bzip2 fam handbook lzma mmx opengl semantic-desktop spell sse sse2 ssl -3dnow -acl (-altivec) (-aqua) -bindist -debug -doc -jpeg2k (-kdeenablefinal) (-kdeprefix) -kerberos -nls -openexr -policykit -test -zeroconf" 0 kB
[ebuild   R   ]  x11-libs/qt-gui-4.6.1  USE="accessibility cups dbus glib gtk mng qt3support tiff (-aqua) -debug -nas -nis -pch -raster -xinerama" 0 kB

Total: 2 packages (2 reinstalls), Size of downloads: 0 kB

[Comment 1 Samuli Suominen (RETIRED) 2010-02-15 16:52:24 UTC]

It isn't really a bug, some code just haven't been fully ported yet. It's marely a warning.

[Comment 2 Matt Whitlock 2010-02-15 17:05:22 UTC]

(In reply to comment #1)
> It isn't really a bug, some code just haven't been fully ported yet. It's
> marely a warning.
> 

Thanks for the response.  Is there a way I could temporarily disable redirecting the stderr of my KDE session to .xsession-errors for the time being?  I don't want a multi-gigabyte log file sitting around.

[Comment 3 Samuli Suominen (RETIRED) 2010-02-15 17:22:53 UTC]

(In reply to comment #2)
> (In reply to comment #1)
> > It isn't really a bug, some code just haven't been fully ported yet. It's
> > marely a warning.
> > 
> 
> Thanks for the response.  Is there a way I could temporarily disable
> redirecting the stderr of my KDE session to .xsession-errors for the time
> being?  I don't want a multi-gigabyte log file sitting around.
> 

ln -nfs /dev/null ~/.xsession-errors

or

rm .xsession-errors ; touch .xsession-errors ; chmod 000 .xsession-errors

(Yes, I know it's lame.)

The .xsession-errors gets setup from /etc/X11/Sessions/Xsession

[Comment 4 Johannes Truschnigg 2010-02-18 16:58:44 UTC]

That bug just made two of my X-sessions crash pretty hard. Symlinking ~/.xsession-errors to /dev/null didn't work, as the symlink got replaced by a regular file upon relogin (which filled up at a rapid pace, too).

[Comment 5 Andreas K. Hüttel 2010-03-12 16:54:42 UTC]

This is not alone a QPainter problem. For example, kate(part) emits several lines of output whenever you select some text with the mouse. Also, starting e.g. okular from a terminal with "okular file.pdf &" makes that terminal pretty useless...

Since this is a real pain for users with disk quota, I'll make it "major". However, it's something that upstream has to fix...

[Comment 6 Davide Pesavento (RETIRED) 2010-04-02 12:34:25 UTC]

Isn't this fixed in 4.4.2?

http://websvn.kde.org/?view=revision&revision=1105396

[Comment 7 Andreas K. Hüttel 2010-04-02 22:30:12 UTC]

(In reply to comment #6)
> Isn't this fixed in 4.4.2?
> 
> http://websvn.kde.org/?view=revision&revision=1105396
> 

It's definitively better than before.

[Comment 8 Andreas K. Hüttel 2010-04-30 20:39:30 UTC]

Still not great, but good enough in 4.4.2 to close this bug I think.