wehttam664 Posted August 23 Share Posted August 23 Hi! I am working with a team for a Forge-powered modded server which, for various technical and logistics reasons, utilizes a custom launcher (specifically a fork of HeliosLauncher). This works well for most of our uses, but specifically our Wayland Linux users (Arch, Fedora, SteamOS, etc.) are unable to start the game due to a crash. This is the entire game log file: Spoiler [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher running: args [<redacted for brevity> --launchTarget, forgeclient, --fml.forgeVersion, 47.2.20, --fml.mcVersion, 1.20.1, --fml.forgeGroup, net.minecraftforge, --fml.mcpVersion, 20230612.114412] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher 10.0.9+10.0.9+main.dcd20f30 starting: java version 17.0.12 by Oracle Corporation; OS Linux arch amd64 version 6.10.3-200.fc40.x86_64 [net.minecraftforge.fml.loading.ImmediateWindowHandler/]: Loading ImmediateWindowProvider fmlearlywindow [EARLYDISPLAY/]: ERROR DISPLAY Failed to initialize graphics window with current settings. Failure details: We are unable to initialize the graphics system. glfwInit failed. If you click yes, we will try and open https://links.minecraftforge.net/early-display-errors in your default browser Most users report that a crash report is never generated by the game, however, there is more information available in the launcher's console: Spoiler /app/main/resources/…ocessbuilder.js:100 [Minecraft] Exception in thread "main" /app/main/resources/…ocessbuilder.js:100 [Minecraft] java.lang.ExceptionInInitializerError /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]+7/org.lwjgl.glfw.GLFW.glfwInit(GLFW.java:1045) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]/net.minecraftforge.fml.earlydisplay.DisplayWindow.initWindow(DisplayWindow.java:346) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]/net.minecraftforge.fml.earlydisplay.DisplayWindow.start(DisplayWindow.java:291) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]/net.minecraftforge.fml.earlydisplay.DisplayWindow.initialize(DisplayWindow.java:154) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]/net.minecraftforge.fml.loading.ImmediateWindowHandler.load(ImmediateWindowHandler.java:48) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]/net.minecraftforge.fml.loading.ModDirTransformerDiscoverer.earlyInitialization(ModDirTransformerDiscoverer.java:43) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.TransformationServicesHandler.lambda$discoverServices$18(TransformationServicesHandler.java:131) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at java.base/java.lang.Iterable.forEach(Iterable.java:75) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.TransformationServicesHandler.discoverServices(TransformationServicesHandler.java:131) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.Launcher.run(Launcher.java:87) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.Launcher.main(Launcher.java:78) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at [email protected]/cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:141) /app/main/resources/…ocessbuilder.js:100 [Minecraft] Caused by: java.lang.NullPointerException: A required function is missing: glfwInitAllocator /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]+7/org.lwjgl.system.APIUtil.requiredFunctionMissing(APIUtil.java:129) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]+7/org.lwjgl.system.APIUtil.apiGetFunctionAddress(APIUtil.java:122) /app/main/resources/…ocessbuilder.js:100 [Minecraft] at MC-BOOTSTRAP/[email protected]+7/org.lwjgl.glfw.GLFW$Functions.<clinit>(GLFW.java:42) In doing research, I found information that Minecraft and Wayland generally don't get along without this patch and these extra JVM options for Forge, but this hasn't helped. It actually looks as though Forge is ignoring my JVM flags and starting its early window anyway. The usual driver and systems updates have been done in all cases to no avail. This issue occurs for a dozen or so of our modpack users on different distros, but all using Wayland. Forge: 47.2.20 Minecraft: 1.20.1 Any ideas? Quote Link to comment Share on other sites More sharing options...
LexManos Posted August 23 Share Posted August 23 Wayland isn't supported in vanilla minecraft until 1.20.2 As for anything the early loading screen does, you can edit the fml.toml to disable it. I dont think the environment variable has been functional since the loading screen rewrite. Quote I do Forge for free, however the servers to run it arn't free, so anything is appreciated. Consider supporting the team on Patreon Link to comment Share on other sites More sharing options...
wehttam664 Posted August 25 Author Share Posted August 25 (edited) On 8/23/2024 at 8:06 PM, LexManos said: Wayland isn't supported in vanilla minecraft until 1.20.2 As for anything the early loading screen does, you can edit the fml.toml to disable it. I dont think the environment variable has been functional since the loading screen rewrite. Thanks for the info. For the toml, I assume you're referring to earlyWindowControl? I tried that setting and it either doesn't work too, or something else is the root cause. We also tried injecting a patched libglfw but it hasn't help either. Unsure if there is a path forward with this still or if the only option is to just upgrade to 1.20.2+. Edited August 25 by wehttam664 Adding a bit more info Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.