RuneJakeKim Posted April 11, 2023 Posted April 11, 2023 Forge gets an error upon launching Log: OpenJDK 64-Bit Server VM warning: getcpu(2) system call not supported by kernel Exception in thread "main" java.lang.module.ResolutionException: Modules lwjgl.glfw.classes and org.lwjgl.tinyfd export package org.lwjgl.util.tinyfd to module coremods at java.base/java.lang.module.Resolver.resolveFail(Unknown Source) at java.base/java.lang.module.Resolver.failTwoSuppliers(Unknown Source) at java.base/java.lang.module.Resolver.checkExportSuppliers(Unknown Source) at java.base/java.lang.module.Resolver.finish(Unknown Source) at java.base/java.lang.module.Configuration.<init>(Unknown Source) at java.base/java.lang.module.Configuration.resolveAndBind(Unknown Source) at java.base/java.lang.module.Configuration.resolveAndBind(Unknown Source) at cpw.mods.bootstraplauncher@1.1.2/cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:129) Java Exit code: 1 Quote
ChampionAsh5357 Posted April 12, 2023 Posted April 12, 2023 Please provide the entire debug.log in the logs folder within the game directory via a gist or pastebin. Quote
warjort Posted April 21, 2023 Posted April 21, 2023 (edited) That is not the logs/debug.log The actual error says you have 2 copies of org.lwjgl.tinyfd somewhere on the classpath and/or in your mods folder. The information you have provided does not say where those 2 implementations are located, though 1 is part of minecraft itself (it uses it for manual loading of resource/data packs). Try without any mods. If that fixes the problem, then you will need to experiment with removing mods to locate which mod causes the problem. If you still have the problem without any mods installed, then the problem is with whatever launcher you are using setting up an incorrect classpath. If you are using the mojang launcher, post the launcher_log.txt If you are using some other launcher, then you will need to contact them. Edited April 21, 2023 by warjort Quote Boilerplate: If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one. If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install Large files should be posted to a file sharing site like https://gist.github.com You should also read the support forum sticky post.
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.