Jump to content

Recommended Posts

Posted

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?

Posted

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.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Posted (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 by wehttam664
Adding a bit more info

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.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • The game crashed whilst unexpected error Error: net.minecraftforge.fml.ModLoadingException: Advanced Mining Dimension (mining_dimension) encountered an error during the done event phase
    • Here is the end of the log. it was way too big to put in pastebin, but I started from when I was online and everything was fine. Error should be in here: https://pastebin.com/Sdhdq593
    • Update: I stand corrected as I was able to dig up a relevant log from my earlier testing which highlights the overall issue but does not explain how to solve it. See, Diagnostic Logs for pack.mcmeta not found: https://pastebin.com/LXS8Rtna
    • Which mod was this? What are all the mods that were in use? It will help if enough information to replicate the problem is available.
    • I have been attempting to create a supplementary resource pack with Patchouli in order to add back the guidebook for Better End but unfortunately in every prototype I have made pack.mcmeta and my resource pack are not recognized. I have tested both zipped and unzipped and either way curseforge does not recognize my resource pack as existing. For testing I stripped my pack down to just the pack.mcmeta file and two empty folders labelled data and assets and I know the data folder is not the problem as firstly my first attempts just had an assets folder following Patchouli instructions and data came later in my flailing attempts to make anything in my pack work. The mcmeta file is not recognized whether or not I use this:  { "pack": { "pack_format": 15, "description": "A replacement for the BetterEnd Guide Book." } "language": { "en_US": { "name": "English", "region": "United States" } } } ,or this:  { "pack": { "pack_format": 15, "description": "A replacement for the BetterEnd Guide Book." } } I have made sure to only use lowercase and the pack folder is named better-end-guide. Is this some magic nonsense from me doing this manually instead of using an IDE or similar tool? Could it be because my files are by default in UTF-8 even though ANSI gives the same results? Is there a specific community secret tool I am supposed to use for zipping or specific settings? I am pulling my hair in distress. Unfortunately as there are no errors involved I lack logs to offer, if that disqualifies this thread please do not be harsh and instead if you can then please direct me to a forum with different rules and sufficiently respectful but knowledgeable as to be of assistance. Most of my experience with the programming community has been poor and so naturally I find myself wary.
  • Topics

  • Who's Online (See full list)

    • There are no registered users currently online
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.