[arch/wayland] 898ebc8 builds successfully, but fails to start
linuxct opened this issue · 7 comments
I have just updated my xava install to the latest commit 898ebc8 pushed to this repo, and it won't start anymore under Sway (wayland mode).
Log when starting xava from cli:
[ERROR] SGLCreateProgram at /home/linuxct/.cache/paru/clone/xava-git/src/xava/src/output/shared/gl_shared.c:371 - Error: linking:
error: fragment shader input `v_color' has no matching output in the previous stage
at /usr/lib/xava/out_wayland.so(+0x6d63) [0x7fecd0d65d63]
at /usr/lib/xava/out_wayland.so(+0x6de0) [0x7fecd0d65de0]
at /usr/lib/xava/out_wayland.so(xavaInitOutput+0x111) [0x7fecd0d64771]
at xava(+0x26a3) [0x55dcabcc66a3]
at /usr/lib/libc.so.6(__libc_start_main+0xd5) [0x7fecd0d9db25]
at xava(+0x2bfe) [0x55dcabcc6bfe]
Relevant lines from my config file:
[general]
framerate = 60
vsync = 0
[window]
transparency = true
keep_below = true
[wayland]
background_layer = true
[output]
method = wayland
Any clue as to why this is happening?
sorry about that, I've changed a lot in terms or rendering.
Old shaders are no longer compatible, you'll have to install new ones. Get them from example_files/gl/shaders.
Its because ive changed the renderer to OGL 4.3 instead of OpenGL ES2
PS: Should've added a note about that.
But if you just dont want to deal with my OpenGL stuff, you could still revert to wayland_sw
for the old "classic" software rendering
I deleted the ~/.config/xava/gl folder and that solved the issue.
Another issue I am having is that now with the new rendering method, is that custom colors seem to not be supported correctly via hexcode for the bars.
[color]
foreground = '#02F723'
looks like
However if I apply foreground = '#FF0000'
, the bars do turn red correctly.
very likely a bug actually, let me investigate
found it, division error in gl_shared.c
Update coming shortly
Pushed an update ;)
Thank you, that solved the issue! :D