Version: unspecified (using KDE 4.5.4) OS: Linux With compositing active, anytime a window miniature should be drawn (e.g. taskbar miniatures, present windows) the system freezes for a few seconds (something like 10s or more) after which the miniature very slowly does appear, although the system is irresponsive. The only way to get back to a working desktop is clicking away from the miniature so it closes, after a few more seconds. This message appears in the console used to start kwin: i915_program_error: Exceeded max instructions (147 out of 123). This only started happening after the upgrade to mesa 7.9. Reproducible: Always Steps to Reproduce: Using an intel gpu activate desktop effects, namely taskbar miniatures. Actual Results: Freeze for a few seconds while drawing miniatures of windows. Expected Results: No freeze. I have mesa 7.9, X.Org X Server 1.9.2 and kernel 2.6.36
i assume it's not the case with "desktop grid"? see bug 243181 and blacklist your gpu - the driver string probably changed witzh teh updated ...4.6 has a GUI way to configure this persistantly.
(In reply to comment #1) > i assume it's not the case with "desktop grid"? > > see bug 243181 and blacklist your gpu - the driver string probably changed > witzh teh updated > ...4.6 has a GUI way to configure this persistantly. You are right. With "desktop grid" there's no problem. I tried adding this to kwinrc: [Blacklist][Lanczos] intel=Mesa DRI Intel(R) 945GME GEM 20100330 DEVELOPMENT x86/MMX/SSE2 :-:1.4 Mesa 7.9 but it didn't made a difference. What exactly am I supposed to do?
Do not "add" a new entry, but append it to the exising Intel ones (or replace the existing entr) and try (notice the uppercase "Intel"): Intel=945GME GEM 20100330:-:7.9 *** This bug has been marked as a duplicate of bug 243181 ***
(In reply to comment #3) > Do not "add" a new entry, but append it to the exising Intel ones There were no Blacklist entries in my kwinrc file. I had to manually add the entry as I said earlier. Should I report that as a bug?
afaik that's a distro/package issue. however you should check whether there's some ~/.kde vs. ~/.kde4 coflict. what does "kde4-config --path config" say about this?