Erro não identificado no PrismLauncher em VoidLinux

Olá pinguins uso void linux tem um tempo na libC musl e percebi que tenho um erro quanto a execução de versões abaixo da 1.13, no caso versões acima dessa rodam de forma perfeita, ao buscar soluções deparei que essas versões utilizam xrandr para serem iniciados, com esse passo concluido o log de retorno torna-se


# log
Prism Launcher version: 9.1 (Void)
Launched instance in online mode
 resolves to:
    [2603:1056:2000:30::, 2603:1057:2:28::2, 2603:1056:2000:30::12, 2603:1057:2:38::, 2603:1056:2000:30::4, 2603:1056:2000:28::1, 2603:1056:2000:30::2, 2603:1056:2000:28::4, 40.126.45.20, 20.190.173.145, 20.190.173.132, 20.190.173.65, 20.190.173.2, 20.190.173.69, 40.126.45.17, 20.190.173.131]

 resolves to:
    [2620:1ec:bdf::33, 13.107.246.33]

resolves to:
    [2620:1ec:bdf::33, 13.107.246.33]


 resolves to:
    [2620:1ec:bdf::33, 13.107.246.33]

Java path is:
/usr/lib/jvm/openjdk8/jre/bin/java


Java is version 1.8.0_332, using 64 (amd64) architecture, from Void.


AMD Ryzen 7 5700U with Radeon Graphics
Advanced Micro Devices, Inc. [AMD/ATI] Lucienne (rev c1)

Subsystem: Acer Incorporated [ALI] Device 152b

Kernel driver in use: amdgpu

Main Class:
  net.minecraft.client.main.Main

Window size: 854 x 480

Launcher: standard

Java Arguments:
[-Xms512m, -Xmx8128m, -Duser.language=en]


Minecraft process ID: 12358


[18:54:19] [Client thread/INFO]: Setting user: none
[18:54:20] [Client thread/INFO]: LWJGL Version: 2.9.4
[18:54:21] [Client thread/INFO]: Reloading ResourceManager: Default
[18:54:21] [Sound Library Loader/INFO]: Starting up SoundSystem...
[18:54:21] [Thread-5/INFO]: Initializing LWJGL OpenAL
[18:54:21] [Thread-5/INFO]: (The LWJGL binding of OpenAL.  For more information, see #)
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00000000000086ae, pid=12358, tid=0x00007f2f89afbb38
#
# JRE version: OpenJDK Runtime Environment (8.0_332-b05) (build 1.8.0_332-b05)
# Java VM: OpenJDK 64-Bit Server VM (25.332-b05 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  0x00000000000086ae
#
# Core dump written.
O processo parou de funcionar com o código 6.

nesse exemplo estou executando a versão 1.10.2

não sei se há uma necessidade do glibC para isso pois nao fiz um chroot, qualquer coisa agradeço os comentarios
(driver fielmente acredito não ser pois as versões acima estam a funcionar)

Olá novamente, utilizei o distrobox rootless e criei dois container do void linux um com glibc e musl e funfou somente no glibc, pessoalmente conclui que o suporte ao musl é limitado, obrigado a todos