Version: 4.3 (using KDE 4.3.0) OS: Linux Installed from: Debian testing/unstable Packages When compositing is enabled, sometimes the title bar of the current application is not refreshed. Example, I use a web browser with few tabs, and after some time the title bar displays the title of the previous browsed tab. Then I click on another tab, and then the title correspond to the tab I've just left etc... On Amarok, the title always says "Amarok 2" instead of displaying the current track title, or displays the previous track's name. If I resize/move the window, the title is ok. I tried different combinations of settings like Opengl/Xrender or Direct rendering, sometimes it looks slightly better, but eventually this bug appears again. Disabling every single desktop effect (wihout disabling compositing) does not help. The only workaround I could find was to disable compositing. I've been able to reproduce this bug on almost every KDE/not KDE/Qt3/Qt4/Gtk application I tried, like Konqueror, dolphin, opera, firefox, Amarok... and on every KDE4.3 platform I tried (Debian Sid 64, Kubuntu 32, Archlinux 64). I couldn't reproduce it with KDE 4.2 on Kubuntu. My graphic card is a GeForce 8600M GT, and I use the nvidia proprietary drivers. The versions of the driver depends on the platform (all above 180).
this is probably related to bug #202642 i'll just blame the pending paint of the idirect deco painting (ARGB deco support) which deco do you use?
I use Ozone, but I have been able to reproduce this with the majority of the standard decorators + aurorae. This might be related to bug #202642, as the "dead maximization button" thing happens only when the titlebar is corrupted. (With BII, because I have no such maximization problems with other decorators)
I'm constantly getting this bug on my macbook, but never on my two desktop computers. All three computers are running Kubuntu Jaunty, and they all have NVidia video cards with proprietary drivers (though different versions). I'll post the video card and driver versions later.
*** This bug has been marked as a duplicate of bug 199735 ***