Unfortunately, I can't provide any more info, except that most of the times this happens, during scrolling, or tooltip appearance. This is using a radeon card and packages for mesa and xorg from xorg-edgers ppa. Reproducible: Always
Sure you can ;-) - What happens when you resize the window? - What happens if you suspend and (afterwards resume) compositing (shift+alt+f12) - (if that does not resume "normal" behavior) do you get a "window does not respond, kill it?" dialog when attempting to close it? - does the "show paint" effect suggest continuing updates in that window? (warning: do not use the effect if you suffer from epilepsy!)
Well, it seems the problem appears when in compositing mode and maximizing the window. Suspend, resuming does not help, and the only way is to kill the application. Paint effect does not show anything weird. Somehow I think the following messages are related: ImageProvider supports Pixmap type but has not implemented requestPixmap() file:///usr/share/kde4/apps/kwin/tabbox/thumbnails/contents/ui/main.qml:135:9: QML Image: Failed to get image from provider: image://client/-1/678061065-0
a) Does "maximizing" mean "maximizing" (with titlebar) or "fullscreen" (w/o titlebar)? b) Does the window at least repaint after suspending the compositor? c) Is it related to the gtk(3) teme (oxygen-gtk?)
Hi again. By maximizing I meant not fullscreen, just pressing the maximize button. Window does not repaint and also I do not have oxygen gtk 3 or 2 packages installed. This freeze also happened without composite enabled. So I am not sure if I am reporting this bug correctly. I have not experienced any such freeze in fvwm, so somehow I think it is related to the kwin. I do not experience such problems if I use fluxbox as a window manager in kde.
Well, I think I spoke too soon. I got a freeze with fluxbox also. So, probably this is not a kwin problem and I am closing this bug.
There might be a specialised gtkrc in KDE sessions, check "env | grep GTK" under KDE and fvwm, then eventually have a look at the used gtkrc files, esp. the hidden user specific ones.
Thanks for the tip. I deleted ~/.kde/share/config/gtkrc and now everything is normal. Thanks again.
Do you still have it? If yes it would be interesting to compare it to figure out which value is responsible.
Unfortunately not. I just deleted the file.
Well it seems I still have this bug. It seems that it hits me randomly.
If the gtkrc was written by some gtkqt kcm or whatever it will likely re-appear whenever you reconfigure it - maybe even autogenerated on startup (though any gtkrc should not freeze a gtk client anyway)