When I maximize a window, sometime the content appears black Reproducible: Sometimes Steps to Reproduce: 1.Maximize a window 2. 3. Actual Results: WHen I maximize a window the content is black. to fix it I have to make the window smaller, then try again Expected Results: see the content of the window when is maximized
if happens to any window is more a problem of kwin. I've seen it happening once or twice, on nvidia drivers. what video drivers are you using?
I bet your left and his right arm on a combo of nvidia drivers and the maximization effect.
in order to figure that one out: please provide output of: qdbus org.kde.KWin /KWin supportInformation
Created attachment 92600 [details] Output of dbus org.kde.KWin /KWin supportInformation
Similar problem for me. I've noticed some additional wrong behavior: Sometimes the maximizing leads to a black window. Mostly happens when using the top edge action to maximize. I subsequently turned that action off. The maximizing, using window decoration button, does what it is expected to do, but when restoring the original window size, with the same maximize decoration button, its content is then entirely black. I will attach the output of qdbus org.kde.KWin /KWin supportInformation for my sstem.
Created attachment 92770 [details] qdbus org.kde.KWin /KWin supportInformation
Using the resize effect and resizing a window out of maximization, I reliably get an invalid texture that remains during the resize. Cutting the clientMaximizedStateChanged signals, the error warning > kwin_core: 0x20084: Texture state usage warning: Texture 0 is base level inconsistent. Check texture size. otherwise only occurs once on the begin and the end of the resize and the texture during the resize is valid. The trigger is crossfading in the maximize effect.
add. > kwin_core: 0x20084: Texture state usage warning: Texture 0 is base level inconsistent. Check texture size. it's actually NOT texture 0 but a real texture (mostly 13, sometimes 19) id that causes the spam
I assume it's a duplicate of bug #324823 *** This bug has been marked as a duplicate of bug 324823 ***