Bug#923226: Compiling shader doesn't work - game doesn't work

[Julien Puydt]

Hi,

Le 07/03/2019 à 18:39, Simon McVittie a écrit :
> On Thu, 07 Mar 2019 at 13:30:57 +0100, Julien Puydt wrote:
>> Just changing the ioquake3 binary package (which makes dpkg complain about
>> ioquake3-server, but it's normal):
>> 1.36+u20181017.09166ba~dfsg-2 works
>> 1.36+u20181222.e5da13f~dfsg-1 fails
> 
> What graphics stack are you using, in particular your kernel and Mesa
> driver? Running `reportbug --template ioquake3` will summarize the most
> relevant packages.
> 
> It looks as though the problem might be that your driver only provides
> GLSL 1.20 (either on your hardware or in general), whereas the hitCube()
> function introduced between 09166ba and e5da13f assumes GLSL 1.30
> or later.
> 

To give more information about the GL stack here, here are exerpts from 
running glxinfo:

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4

client glx vendor string: Mesa Project and SGI
client glx version string: 1.4

GLX version: 1.4

Extended renderer info (GLX_MESA_query_renderer):
     Vendor: Intel Open Source Technology Center (0x8086)
     Device: Mesa DRI Intel(R) Ironlake Mobile  (0x46)
     Version: 18.3.4
     Accelerated: yes
     Video memory: 1536MB
     Unified memory: yes
     Preferred profile: compat (0x2)
     Max core profile version: 0.0
     Max compat profile version: 2.1
     Max GLES1 profile version: 1.1
     Max GLES[23] profile version: 2.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile
OpenGL version string: 2.1 Mesa 18.3.4
OpenGL shading language version string: 1.20

OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.3.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16


Hope that helps,

jpuydt on irc.debian.org