CBWright

That did it! I don't know what happened to that directory though. It was owned by my account, but I had to go into root to delete it. Anyway, it installed without issue after that. Sorry for the trouble.

the /forgespi directory is empty...

... I'm a little embarrassed, since the log file is RIGHT UNDER THE INSTALL FILE. Sigh. Apologies. Pastebin of log here: https://pastebin.com/E0XF24Sv

When I try to install the jar for 1.14.4-28.0.1 I get the following message: I wondered if maybe there was a typo, and "forgespi" should actually be "forgeapi" -- the a and s are right next to each other on the keyboard so it seemed plausible. I assumed there wasn't a log file generated for the installer, so I didn't try to capture one.

Is there a way to close/mark a thread as resolved? I was finally able to confirm last night that, as per treebranch's suggestion, I could simply configure each individual entry in the minecraft launcher to point to the openjdk 8 executable in /usr/lib and it launched fine, even with openjdk 11 installed as well. So this issue is now completely and thoroughly a non-issue. ? Thanks all.

Yep, that was the problem! I had both OpenJDK 11 and 8 installed on my machine. In the past Minecraft always defaulted to using 8 so I never really thought about it. I removed 11 and Minecraft with Forge runs fine. So now that I know that, when I get home I'll take treebranch's advice, to into the settings on my other machine, and configure minecraft to use the v8 executable, see how that goes.

I spent some time trying to figure this out last night, and made very little progress. I'm not sure what my next steps are, but I hope this information is useful to someone: 1.13.2-forge-25.0.146 crashes on two separate Linux machines, but runs just fine on my Windows machine. The most obvious difference between the two, other than Windows vs Linux, is that the Windows machine uses Oracle Java and the Linux machines use openjdk Here is a pastebin for the lastest log file: https://pastebin.com/Dr1V0QQZ No crash report is generated when this crash occurs (the last crash-reports file I have in my directory has a timestamp of 2019-04-06) This current log file is for a machine that has plugins loaded in it, but on my other Linux machine I deleted all my plugins and still got a crash. I can load vanilla 1.13.2 (no Forge) and it works fine Attempting to "back out" to a lower version of Forge still causes a crash. I suspect, though, that in that case I simply don't know how to clean up my minecraft environment properly. This is an observation only (so perhaps unreliable), but when I first installed .146 and fired it up in the launcher, it started downloading the extra files it needed, and the window closed before the progress bar indicated it was finished. A few seconds later the crash dialog came up. Ever since then, the crash dialog appears almost immediately after I click the launch button. So I wondered if perhaps it hadn't finished downloading the extra components it needs? Not sure how to verify that, though. If there's a way to get that information to you I'm happy to do so, I just need someone to tell me how.

If you're seeing a 0kb file and you don't know why, there's a pretty solid chance you're using Firefox. Firefox has been flagging Forge files as malware for every version of Forge after .108 (for 1.13.2 releases), but unlike Chrome, which tells you what's happening and makes it obvious, all Firefox does is place a little yellow dot in the download notification icon (see attached). You have to open that menu and click on the "more information link" under the file it flagged, at which point Firefox will say OMG THIS FILE IS GOING TO DESTROY YOUR COMPUTER PROBABLY but it gives you the option to either delete the file or open it. If you choose to open the file and then click cancel on the dialog box that follows the file will be the the proper, correct size and you can use it normally.

Firefox is reporting the same kind of problem, but not for every file on forge. It is specifically reporting it for forge-1.13.2.25.0.110-installer.jar, but downloads 1.13.2.25.0.108-installer jar without any complaints or warnings.

(Disclaimer: this is my first attempt at reporting a bug. Hopefully it's EAQ compliant, I went and got a Pastebin account specifically to do this...) WIT and similar mods (like Hwyla) work when I run Forge 1.13.2-25.0.60. Any version after that and Minecraft generates the following error message: (similar message generated when I try to use Hwyla.) So far I have been able to determine: I am using the mod specifically released for 1.13.2 I am running OpenJDK 8 on KDE Neon (Ubuntu 18.04 base) Removing WIT from the mods folder resolves the issue Here is the pastebin of the latest.log file. https://pastebin.com/zZeUU076 (The EAQ specifies a debug.log file - I have not found one in the logs directory. Hopefully this is the same file?)