Error: GLSL 3.30 is not supported

[gitmac777]

Hello, use a ROCK64 single-board computer (RK3328 Quad-Core ARM Cortex A53 64-Bit Processor), ARM Mali-450MP2 Dual-core GPU, OpenGL ES 1.1 and 2.0, OpenVG1.1.

Alacritty had only ever worked with swrast driver (including input latency).

Now it doesn't work anymore after upgrade kernel to v5.6.2:
Alacritty encountered an unrecoverable error:
There was an error initializing the shaders: Failed compiling shader at /home/buildozer/aports/community/alacritty/src/alacritty-0.4.0/alacritty_terminal/../res/text.v.glsl: 0:14(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES

With MESA_GL_VERSION_OVERRIDE=3.3 and MESA_GLSL_VERSION_OVERRIDE=330:
Alacritty encountered an unrecoverable error:
There was an error initializing the shaders: Failed linking shader: error: output location 0 >= GL_MAX_DUAL_SOURCE_DRAW_BUFFERS with index 1 for alphaMask

[chrisduerr]

Seems like a duplicate of #128? Alacritty requires a GPU capable of running GLSL 3.30 or higher.

[gitmac777]

I tested the recommendations from #128 and it didn't work, maybe I missed something?
I am currently using sway and it does not start with LIBGL_ALWAYS_SOFTWARE=1.

[kchibisov]

you should start just alacritty with LIBGL_ALWAYS_SOFTWARE=1 alacritty (not entire sway), seems to use SW for me. What error does it give to you with mentioned env var?

[gitmac777]

Yes then it works fine. Shame on me

[rabitt88]

How to set LIBGL_ALWAYS_SOFTWARE=1 alacritty as shortcut?

[scalarwaves]

@rabitt88 In my sway config I have:
set $term-float LIBGL_ALWAYS_SOFTWARE=1 alacritty
bindsym $mod+Return exec $term-float

Now mod+ENTER loads alacritty

[dramosgo]

Add it as environmental variable: edit (as root) /etc/environment and add:
LIBGL_ALWAYS_SOFTWARE=true
Save, logout and login back. Now you can run alacritty from everywhere.
Enjoy!

[SatouKuzuma1]

@dramosgo after doing this: LIBGL_ALWAYS_SOFTWARE=true, and log out, when I boot up again I can-'t open alacritty. I have to run the command again. Is there any solution to this? I have the same problem with kitty.

[sskras]

@SatouKuzuma1 commented on May 1:

@dramosgo after doing this: LIBGL_ALWAYS_SOFTWARE=true, and log out, when I boot up again I can-'t open alacritty. I have to run the command again.

This is because the variable is lost when you close your current shell (terminal session).

Is there any solution to this? I have the same problem with kitty.

You could set it from some automatic shell mechanisms (per-user or per-system).
Like one mentioned by @dramosgo on Dec 24, 2021:

Add it as environmental variable: edit (as root) /etc/environment and add: LIBGL_ALWAYS_SOFTWARE=true Save, logout and login back. Now you can run alacritty from everywhere. Enjoy!