Posted August 14, 20187 yr I'm trying to install Minecraft Forge on Linux (CLIENT, NOT SERVER). The install succeeds, but ends up crashing after I start the game. I can manage to start up vanilla 1.12.2 though. This leaves absolutely nothing in debug.log in ~/.minecraft/logs. There is literally no file to share. Here's the log for the installer though. > java -jar forge-1.12.2-14.23.4.2750-installer.jar Spoiler java.net.preferIPv4Stack=true Considering library net.minecraftforge:forge:1.12.2-14.23.4.2750: Not Downloading {Wrong Side} Considering library net.minecraft:launchwrapper:1.12: Not Downloading {Wrong Side} Considering library org.ow2.asm:asm-all:5.2 Downloading library org.ow2.asm:asm-all:5.2 Trying unpacked library org.ow2.asm:asm-all:5.2 Considering library org.jline:jline:3.5.1: Not Downloading {Wrong Side} Considering library net.java.dev.jna:jna:4.4.0: Not Downloading {Wrong Side} Considering library com.typesafe.akka:akka-actor_2.11:2.3.3 Downloading library com.typesafe.akka:akka-actor_2.11:2.3.3 Unpacking packed file akka-actor_2.11-2.3.3.jar.pack.xz Signed Checksum Length: 140942 Total Length: 2606968 Temp File: /tmp/art3719451471352066484.pack Successfully unpacked packed file akka-actor_2.11-2.3.3.jar.pack.xz Checking "/home/gabriel/.minecraft/libraries/com/typesafe/akka/akka-actor_2.11/2.3.3/akka-actor_2.11-2.3.3.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library com.typesafe:config:1.2.1 Downloading library com.typesafe:config:1.2.1 Unpacking packed file config-1.2.1.jar.pack.xz Signed Checksum Length: 12246 Total Length: 111476 Temp File: /tmp/art17314088556115459095.pack Successfully unpacked packed file config-1.2.1.jar.pack.xz Checking "/home/gabriel/.minecraft/libraries/com/typesafe/config/1.2.1/config-1.2.1.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-actors-migration_2.11:1.1.0 Downloading library org.scala-lang:scala-actors-migration_2.11:1.1.0 Unpacking packed file scala-actors-migration_2.11-1.1.0.jar.pack.xz Signed Checksum Length: 3311 Total Length: 52481 Temp File: /tmp/art11132463154823223125.pack Successfully unpacked packed file scala-actors-migration_2.11-1.1.0.jar.pack.xz Checking "/home/gabriel/.minecraft/libraries/org/scala-lang/scala-actors-migration_2.11/1.1.0/scala-actors-migration_2.11-1.1.0.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-compiler:2.11.1 Downloading library org.scala-lang:scala-compiler:2.11.1 Unpacking packed file scala-compiler-2.11.1.jar.pack.xz Signed Checksum Length: 942120 Total Length: 9183051 Temp File: /tmp/art10984587656039038773.pack Successfully unpacked packed file scala-compiler-2.11.1.jar.pack.xz Checking "/home/gabriel/.minecraft/libraries/org/scala-lang/scala-compiler/2.11.1/scala-compiler-2.11.1.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang.plugins:scala-continuations-library_2.11:1.0.2 Downloading library org.scala-lang.plugins:scala-continuations-library_2.11:1.0.2 Unpacking packed file scala-continuations-library_2.11-1.0.2.jar.pack.xz Signed Checksum Length: 2416 Total Length: 18871 Temp File: /tmp/art6449395633029606409.pack Successfully unpacked packed file scala-continuations-library_2.11-1.0.2.jar.pack.xz Checking "/home/gabriel/.minecraft/libraries/org/scala-lang/plugins/scala-continuations-library_2.11/1.0.2/scala-continuations-library_2.11-1.0.2.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang.plugins:scala-continuations-plugin_2.11.1:1.0.2 Downloading library org.scala-lang.plugins:scala-continuations-plugin_2.11.1:1.0.2 Unpacking packed file scala-continuations-plugin_2.11.1-1.0.2.jar.pack.xz Signed Checksum Length: 16815 Total Length: 139418 Temp File: /tmp/art18279556076143661085.pack Successfully unpacked packed file scala-continuations-plugin_2.11.1-1.0.2.jar.pack.xz Checking "/home/gabriel/.minecraft/libraries/org/scala-lang/plugins/scala-continuations-plugin_2.11.1/1.0.2/scala-continuations-plugin_2.11.1-1.0.2.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-library:2.11.1 Downloading library org.scala-lang:scala-library:2.11.1 Unpacking packed file scala-library-2.11.1.jar.pack.xz Signed Checksum Length: 341368 Total Length: 5984083 Temp File: /tmp/art4444774882677561046.pack Successfully unpacked packed file scala-library-2.11.1.jar.pack.xz Checking "/home/gabriel/.minecraft/libraries/org/scala-lang/scala-library/2.11.1/scala-library-2.11.1.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-parser-combinators_2.11:1.0.1 Downloading library org.scala-lang:scala-parser-combinators_2.11:1.0.1 Unpacking packed file scala-parser-combinators_2.11-1.0.1.jar.pack.xz Signed Checksum Length: 37614 Total Length: 273457 Temp File: /tmp/art11705955907229889440.pack Successfully unpacked packed file scala-parser-combinators_2.11-1.0.1.jar.pack.xz Checking "/home/gabriel/.minecraft/libraries/org/scala-lang/scala-parser-combinators_2.11/1.0.1/scala-parser-combinators_2.11-1.0.1.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-reflect:2.11.1 Downloading library org.scala-lang:scala-reflect:2.11.1 Unpacking packed file scala-reflect-2.11.1.jar.pack.xz Signed Checksum Length: 291610 Total Length: 3217021 Temp File: /tmp/art10498841924588019797.pack Successfully unpacked packed file scala-reflect-2.11.1.jar.pack.xz Checking "/home/gabriel/.minecraft/libraries/org/scala-lang/scala-reflect/2.11.1/scala-reflect-2.11.1.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-swing_2.11:1.0.1 Downloading library org.scala-lang:scala-swing_2.11:1.0.1 Unpacking packed file scala-swing_2.11-1.0.1.jar.pack.xz Signed Checksum Length: 39019 Total Length: 888907 Temp File: /tmp/art8974381606522032053.pack Successfully unpacked packed file scala-swing_2.11-1.0.1.jar.pack.xz Checking "/home/gabriel/.minecraft/libraries/org/scala-lang/scala-swing_2.11/1.0.1/scala-swing_2.11-1.0.1.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-xml_2.11:1.0.2 Downloading library org.scala-lang:scala-xml_2.11:1.0.2 Unpacking packed file scala-xml_2.11-1.0.2.jar.pack.xz Signed Checksum Length: 35380 Total Length: 739509 Temp File: /tmp/art3980170355487266793.pack Successfully unpacked packed file scala-xml_2.11-1.0.2.jar.pack.xz Checking "/home/gabriel/.minecraft/libraries/org/scala-lang/scala-xml_2.11/1.0.2/scala-xml_2.11-1.0.2.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library lzma:lzma:0.0.1: Not Downloading {Wrong Side} Considering library net.sf.jopt-simple:jopt-simple:5.0.3: Not Downloading {Wrong Side} Considering library java3d:vecmath:1.5.2 Downloading library java3d:vecmath:1.5.2 Trying unpacked library java3d:vecmath:1.5.2 Considering library net.sf.trove4j:trove4j:3.0.3 Downloading library net.sf.trove4j:trove4j:3.0.3 Trying unpacked library net.sf.trove4j:trove4j:3.0.3 Considering library org.apache.maven:maven-artifact:3.5.3 Downloading library org.apache.maven:maven-artifact:3.5.3 Trying unpacked library org.apache.maven:maven-artifact:3.5.3 Extracting: /forge-1.12.2-14.23.4.2750-universal.jar To: /home/gabriel/.minecraft/libraries/net/minecraftforge/forge/1.12.2-14.23.4.2750/forge-1.12.2-14.23.4.2750.jar
August 14, 20187 yr Author After taking a closer look at my ~/.minecraft/versions/ folder, I realized that forge is not installing an actual .jar file. Weird.
August 14, 20187 yr The jar doesn't actually go in the versions folder 2 hours ago, Kaisogen said: Extracting: /forge-1.12.2-14.23.4.2750-universal.jar To: /home/gabriel/.minecraft/libraries/net/minecraftforge/forge/1.12.2-14.23.4.2750/forge-1.12.2-14.23.4.2750.jar This looks correct. If you don't have a debug.log could you provide a launcher.log launcher_log.txt? It would be in .minecraft . Note: I'm going off of Windows experience here so I don't know if Linux even has a native MC launcher or is still using the old Jar launcher, the file might not even exist. Edited August 14, 20187 yr by DaemonUmbra Corrected file name This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub. When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore]
August 14, 20187 yr Posting since I'm a linux user as well, and figured I might be able to help In my .minecraft folder there is not a launcher.log file, though I do have a file named "launcher_log.txt which I assume fulfills the same purpose. In ~/.minecraft/logs there is "debug.log" and "latest.log", in addition to compressed files such as 2018-08-14-1.log.gz which uncompresses into a log file. Launcher wise, I imagine most people are still using the old launcher since I don't think there was an update prompt like on Windows, but Mojang released the new launcher as a .tar.gz for everyone, a .deb file for Debian based distros, and as an AUR package for the arch users so it certainly is out there. Edit: going to look into this some more since I have time, what distro are you using @Kaisogen? I have a fresh version of Manjaro that I installed Minecraft onto earlier today, and then Forge, no errors. Edited August 14, 20187 yr by Fijal
August 17, 20187 yr Author On 8/14/2018 at 4:55 PM, Fijal said: Posting since I'm a linux user as well, and figured I might be able to help In my .minecraft folder there is not a launcher.log file, though I do have a file named "launcher_log.txt which I assume fulfills the same purpose. In ~/.minecraft/logs there is "debug.log" and "latest.log", in addition to compressed files such as 2018-08-14-1.log.gz which uncompresses into a log file. Launcher wise, I imagine most people are still using the old launcher since I don't think there was an update prompt like on Windows, but Mojang released the new launcher as a .tar.gz for everyone, a .deb file for Debian based distros, and as an AUR package for the arch users so it certainly is out there. Edit: going to look into this some more since I have time, what distro are you using @Kaisogen? I have a fresh version of Manjaro that I installed Minecraft onto earlier today, and then Forge, no errors. Hey, sorry for the late response. I'm using Linux Mint 19, Cinnamon. I am using the .deb new launcher. I deleted the .minecraft folder, reinstalled the .deb, and reinstalled forge, and tried to start one more time before sending the logs. launcher_log.txt latest.log
August 17, 20187 yr debug.log has more information than latest.log, but I have a hunch... are you running the game fullscreen? If so try going into options.txt and setting fullscreen to false. This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub. When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore]
November 1, 20187 yr I know this is a rather old thread, but I've encountered the same problem and managed to fix the issue. For me the reason for this is because Linux Mint uses a newer version of Java, namely Java 10 .. You can see this by opening a terminal and typing: java --version For me this showed something with openjdk ... version 10 To fix this simply open the terminal and enter: sudo update-alternatives --config java This should give you a screen where you can select other versions of java.. I chose option 2, which is, as of this time, Java 8.. After this and a reboot, Minecraft with Forge is working fine through the newest launcher
September 26, 20196 yr @Da9L I know it's again a rather long time, but thank you very much for your answer. Had a little trouble too to get it to work after again trying Minecraft after a long time and I absolutely wanted to install forge again. Didn't even think about the standard executables. Many dist upgrades between now and the last time I played
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.