Bug 284984 - When Blur is set to max, pink bullets appear on blurred areas on Intel i915
Summary: When Blur is set to max, pink bullets appear on blurred areas on Intel i915
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-26 07:30 UTC by Kai Uwe Broulik
Modified: 2012-04-18 16:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Pink bullets on blurred areas (150.99 KB, image/png)
2011-10-26 07:30 UTC, Kai Uwe Broulik
Details
GLXINFO (12.03 KB, text/plain)
2011-10-26 07:30 UTC, Kai Uwe Broulik
Details
glxinfo -l (15.02 KB, text/plain)
2011-10-27 09:50 UTC, Kai Uwe Broulik
Details
glxinfo -l with mesa 8.0.2 (15.22 KB, text/plain)
2012-04-06 11:27 UTC, Kai Uwe Broulik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2011-10-26 07:30:14 UTC
Created attachment 64875 [details]
Pink bullets on blurred areas

Version:           unspecified (using KDE 4.7.2) 
OS:                Linux

When I set Blur strength to maximum, I get pink bullets and painting issues on blurred areas (panel, plasma extenders).
Mesa 7.11 on Kubuntu 11.10, Intel i915 driver.
When I change blur strength back to another value, the issue vanishes.

Reproducible: Always

Steps to Reproduce:
1. Have an Intel graphics with i915 driver
2. Set blur strength to maximum

Actual Results:  
Panel, plasma extenders, etc. (blurred areas) get pink bullets drawn over them.

Expected Results:  
Panel is really blurred
Comment 1 Kai Uwe Broulik 2011-10-26 07:30:30 UTC
Created attachment 64876 [details]
GLXINFO
Comment 2 Martin Flöser 2011-10-26 15:28:02 UTC
could you add an "glxinfo -l" output.
Comment 3 Kai Uwe Broulik 2011-10-27 09:50:34 UTC
Created attachment 64938 [details]
glxinfo -l
Comment 4 Thomas Lübking 2011-11-14 14:53:43 UTC
It's most likely an indirection issue and i somehow doubt this:
> GL_MAX_PROGRAM_ALU_INSTRUCTIONS_ARB = 16384
> GL_MAX_PROGRAM_TEX_INSTRUCTIONS_ARB = 16384
> GL_MAX_PROGRAM_TEX_INDIRECTIONS_ARB = 16384
> GL_MAX_PROGRAM_NATIVE_ALU_INSTRUCTIONS_ARB = 16384
> GL_MAX_PROGRAM_NATIVE_TEX_INSTRUCTIONS_ARB = 16384
> GL_MAX_PROGRAM_NATIVE_TEX_INDIRECTIONS_ARB = 16384

... a lot ;-)

Native one should be more like "4", so there's likely sth. broken in the driver/setup.

Is the issue still existent?
Comment 5 Martin Flöser 2011-11-14 18:12:58 UTC
> It's most likely an indirection issue and i somehow doubt this:
> > GL_MAX_PROGRAM_ALU_INSTRUCTIONS_ARB = 16384
> > GL_MAX_PROGRAM_TEX_INSTRUCTIONS_ARB = 16384
> > GL_MAX_PROGRAM_TEX_INDIRECTIONS_ARB = 16384
> > GL_MAX_PROGRAM_NATIVE_ALU_INSTRUCTIONS_ARB = 16384
> > GL_MAX_PROGRAM_NATIVE_TEX_INSTRUCTIONS_ARB = 16384
> > GL_MAX_PROGRAM_NATIVE_TEX_INDIRECTIONS_ARB = 16384
> 
> ... a lot ;-)
yeah that's what I thought as well, when I looked at the numbers. At least 
with these the shader should not hit any limits :-)
Comment 6 Kai Uwe Broulik 2011-12-23 12:54:17 UTC
In 4.8 the pink bullets only appear when disabling the new "Save intermediate rendering results".
When this option is checked, everything works fine, if it is not checked, the bullets appear as stated above.
Comment 7 Kai Uwe Broulik 2012-04-06 10:52:25 UTC
Seems to work now on
OpenGL version string: 2.1 Mesa 8.0.2
:-)
Comment 8 Martin Flöser 2012-04-06 10:54:28 UTC
ah an upstream which is upstream.

just for the record: could you please attach a glxinfo -l so that we can see whether the values are correct, now?
Comment 9 Kai Uwe Broulik 2012-04-06 11:27:11 UTC
Created attachment 70185 [details]
glxinfo -l with mesa 8.0.2
Comment 10 Martin Flöser 2012-04-06 11:31:50 UTC
The values look pretty much the same as before.
Comment 11 Thomas Lübking 2012-04-06 14:49:50 UTC
couple of ARB limits were indeed raised what might be related
-    GL_NUM_COMPRESSED_TEXTURE_FORMATS_ARB = 6
+    GL_NUM_COMPRESSED_TEXTURE_FORMATS_ARB = 2
-        GL_MAX_PROGRAM_PARAMETERS_ARB = 1024
+        GL_MAX_PROGRAM_PARAMETERS_ARB = 4096
-        GL_MAX_PROGRAM_LOCAL_PARAMETERS_ARB = 1024
+        GL_MAX_PROGRAM_LOCAL_PARAMETERS_ARB = 4096
-        GL_MAX_PROGRAM_LOCAL_PARAMETERS_ARB = 1024
+        GL_MAX_PROGRAM_LOCAL_PARAMETERS_ARB = 4096
-        GL_MAX_VERTEX_UNIFORM_COMPONENTS_ARB = 4096
+        GL_MAX_VERTEX_UNIFORM_COMPONENTS_ARB = 16384
-        GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS_ARB = 0
+        GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS_ARB = 16
-        GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS_ARB = 16
+        GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS_ARB = 32
-        GL_MAX_FRAGMENT_UNIFORM_COMPONENTS_ARB = 4096
+        GL_MAX_FRAGMENT_UNIFORM_COMPONENTS_ARB = 16384
Comment 12 Kai Uwe Broulik 2012-04-18 16:10:51 UTC
It seems Blur’s caching capabilities are quite minimizing this issue but I was playing around a bit and the issue is still present. Sorry for the noise.