View source for SeaMonkey/KDE/Debugging GTK UI rendering in KDE4

= Debugging GTK UI rendering in KDE4 =

There're several things in KDE4, that can affect UI rendering.
Each of them should be checked whether it triggers the bug.
Any additional information could help to narrow the issue.

== Desktop Effects ==
KDE4 supports different window composition backends. They're controlled in SystemSettings / Desktop / Desktop Effects:

 http://bcchang.com/immersive_blog/wp-content/uploads/2009/09/system-settings-desktop.jpg

Try Enable/Disable it and check whether this triggers bug.
In "Anvanced" options, when effects are enabled try different compositing backends (XRender, OpenGL...)
No need to restart, just change the setting and hit "Apply" button.

== Video Driver ==
If possible, try using different video driver and check whether this affects the bug. I.e. try nouveau instead nvidia, or try booting vesa.

== GTK rendering ==
KDE4 allows to configure look of GTK applications: SystemSettings / Appearance / GTK+ Appearance:

 http://img.vivaolinux.com.br/imagens/artigos/comunidade/kde4aparencia13.png

If it's not there install the correct kde config module:
* Debian: <tt>apt-get install kde-config-gtk-style</tt>
* Ubuntu: <tt>aptitude install kde-config-gtk</tt>
* Fedora: <tt>yum install kcm-gtk</tt>
Try different widget styles (oxygen-gtk, qt-curve...) and check whether bug disappears when you change widget style.

Note: those settings are saved in file <tt>~/.gtkrc-2.0-kde*</tt> so if you want to undo the changes just delete that file.

== GTK environment ==
---------------
Trying to make GTK apps look same as KDE apps KDE4 changes GTK styles using environment variables <tt>GTK_RC_FILES</tt> and <tt>GTK2_RC_FILES</tt>. Check whether anything changes when you unset it. To check that run your testprogram like this:
<tt>env GTK_RC_FILES="" GTK2_RC_FILES="" testprogram</tt>

== No KDE ==
If nothing else affects the bug try booting without KDE. For example install some small desktop environment (e.g. icewm) or select in X Safe Mode session on login screen and check whether the bug is still there.

== LiveCD ==
If all previous attemts failed it could be that some part of your system or settings is to blame. To check that try booting from a LiveCD and check whether the bug can be reproduced there.

''This article originally written by fedorauser''