Version: unspecified (using KDE 4.6.2) OS: Linux After my computer has been running for a while everything including windows, background and panel is drawn wrong. I see large "pixels" and e.g. Firefox is unreadable. Restarting applications works for the applications, but I have found no way to redraw the background and the panel. I add an attachement to show how it looks. This problem only appears on my desktop, and it only started after I got a bigger screen. I now have a 24" screen with 1900x1200 resolution, and I am using Intel integrated graphics card 82945G/GZ. I understand that this might very well not be a KWin issue, but please understand that it is also very difficult for me as a novice user to understand where to report the bug. Please inform me where to redirect it if it is not an issue with KWin, and please let me know if I can provide further details! Reproducible: Didn't try Steps to Reproduce: Start the machine, leave it running for 10-20 hours or thereabout. Actual Results: Drawing errors Expected Results: No drawing errors
Created attachment 59598 [details] showing the redrawing issues
First of all: use "sensors" and CHECK THE TEMPERATURE of the CPU and the chipset! (your "graphics card" is the display adapter component or the 945G chipset) To figure KWin relevance: Do you use compositing? (cause it doesn't look like - solid panel, no shadow/real glow) (Hint: when attaching illustrating screenshots, please rather use jpeg than scaling them down - firefox looks a bit like it was passed through a linear scale filter, that's hard/impossible to say from this shot.)
Thank you for the quick reply! Sorry about the png, I will add a jpeg shortly. I checked sensors, and I see no problems but I think perhaps I do not have that many sensors (the computer is now about 4 years old): $ sensors smsc47b397-isa-0480 Adapter: ISA adapter fan1: 1812 RPM fan2: 0 RPM fan3: 0 RPM fan4: 1072 RPM temp1: +44.0°C temp2: +0.0°C temp3: +30.0°C temp4: +0.0°C
Created attachment 59644 [details] showing the redrawing issues, jpeg format
The temperatures are uncritical - i assume this is from a time when the issue occurs? While you didn't mention, from the new screenshot (the format isn't actually that important - just downscaling is bad to illustrate graphical issues ;-) i'm pretty confident that you're *not* using any type of compositing, what makes this pretty much a driver bug (or broken HW) only and for sure (thus marking the bug upstream) An interesting aspect is that FF is affected as well as the desktop, but (apparently) not the panel or the window titlebar (kwin decoration). - Is the issue related to a specific client being present (ie. only occurs if eg. FF is running)? - does "xprop -root | grep -i color" print anything? Driver bugs are tracked at http://bugs.freedesktop.org
"I assume this is from a time when the issue occurs?" Yes, correct. "I'm pretty confident that you're *not* using any type of compositing" Correct again. "An interesting aspect is that FF is affected as well as the desktop, but (apparently) not the panel or the window titlebar (kwin decoration)." Actually the panel is also affected, it is just not as visible in the screenshot. "- Is the issue related to a specific client being present (ie. only occurs if eg. FF is running)?" A bit difficult to say, but I do not get the impression that that is the case. "- does "xprop -root | grep -i color" print anything?" Yes, quite a lot. I'll attach the output. Thanks for your info, I will have a look at the freedesktop link you gave me.
Created attachment 59689 [details] output from xprop
The xprop is harmless - i expected sth. like a custom color table on the root window. Since you're not using compositing, this is definitively no kwin issue. If you think it's related to FF - do you use FF layer acceleration or webgl? ("about:config", filter for "layer" and "webgl"
webgl.disabled is set to false, which means it's activated? The same for layers.acceleration.disabled. OK, I have no idea what xprop is, but thanks for checking for me ;)
OK, webgl is -probably- harmless since it's only used on very few and special (rather demo) pages, but you might try to set layers-accelerate-all : false layers-acceleration.disabled : true layers-acceleration.force-enabled : false and see whether this has any impact on your issue