Created attachment 129162 [details] glxinfo > glxinfo.txt Many applications including glxinfo show these messages in console : pp: Failed to translate a shader for depth1fs pp: Failed to translate a shader for blend2fs pp: Failed to translate a shader for color1fs pp: Failed to translate a shader for blend2fs I was unable to figure out what component pp belongs to, so choose the driver for my card. mesa-git master, commit f8f7ea508b . ./autogen.sh --prefix=/usr \ --sysconfdir=/etc \ --with-dri-driverdir=/usr/lib/xorg/modules/dri \ --with-gallium-drivers=i915,ilo,r300,r600,radeonsi,nouveau,svga,swrast,virgl \ --with-dri-drivers=i915,i965,r200,radeon,nouveau,swrast \ --with-egl-platforms=x11,drm,wayland \ --with-vulkan-drivers=intel,radeon \ --with-sha1=libnettle \ --enable-texture-float \ --enable-osmesa \ --enable-xa \ --enable-nine \ --disable-xvmc \ --enable-vdpau \ --enable-omx \ --enable-opencl \ --enable-opencl-icd \ --enable-glx-tls glxinfo output (without the pp messages) attached
Try to disable post processing in drirc.
After seeing marek reply I experimented a bit with PP_DEBUG and post processing filters. Half of the error messages comes from pp_jimenezmlaa filter , the other half from pp_jimenezmlaa_color . disabling those filters through driconf does make the corresponding error messages disappear. The error messages started recently, want me to try bisecting to find out what caused them ?
That's up to you. I'm not so into fixing the postprocessing, because the options shouldn't be put into drirc, because the filters change what the OpenGL spec specifies.
Fixed by: author Marek Olšák <marek.olsak@amd.com> commit 8cd58df2f2592bf5a19ef7431eccaca6b8a445cc gallium/pp: fix MLAA shaders Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99549
Patch was reverted
Sorry, posted on the wrong bug
when will this fix come to mesa fixes release 17.x and 18.x? thx for the fix
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.