search

TeamAOF / All-of-Fabric-5

Modpack containing the latest & best of Fabric.
52 stars 28 forks source link

Modpack crashing during launch under Linux #507

Open ghost opened 2 years ago

ghost commented 2 years ago

I got the issue that the modpack is crashing while launching under linux. I also can't seem to figure out a reason to why it does not work. At first I thought that this could maybe be due to sodium, iris and other heavy client changing mods being installed, but after quick testing I found out that, this is not the case. Maybe someone here could help me to find a fix for this?

System specifications: OS: Arch Linux x86_64 Kernel: 6.0.2-arch1-1 DE: Plasma 5.26.1 WM: KWin CPU: AMD Ryzen 5 3600 (12) @ 3.600GHz Memory: 32008MiB GPU: NVIDIA Geforce GTX 1660 Super Java: openjdk 17.0.5 2022-10-18

Logs latest.log: https://pastebin.com/X1gJvacH hs_err_pid: https://controlc.com/f8b90e98 (Since pastebin instantly removes my paste of this file, I had to use another provider)

TheRealKANi commented 2 years ago

I have the same issue on ubuntu 22.04 with GD Launcher, i suspect it has something to do with LWJGL, my instance is also just stopping right after client.properties in your lavest.log, the last two lines.. btw.. your hs_err log has expired on pb.. Will post specs and logs of my sys later.

legoatoom commented 2 years ago

https://pastebin.com/aeQEXGL6 Also got errors. Once in a blue moon it does run. I tried using a different JVM (openjdk), same problem.

TheRealKANi commented 2 years ago

https://pastebin.com/aeQEXGL6 Also got errors. Once in a blue moon it does run. I tried using a different JVM (openjdk), same problem.

Just browsed thru your log.. found one intresting thing..

Line 1235: Event: 21.655 Thread 0x00007f73e426be00 Exception <a 'java/lang/ClassNotFoundException'{0x000000064b90fbf8}: groovy/lang/GroovyShellCustomizer> (0x000000064b90fbf8)

Just realized you said once in a blue moon.. IF if is just a missing source file from groovy, why would it be intermittent..

legoatoom commented 2 years ago

Just realized you said once in a blue moon..

It is quite weird. From the limited testing I did it seems to work once every time I restart the PC, if the PC has been off for a while. Although it could also be just a coincidence and my brain making patterns that are not there.

For now I decided to run the previous version of the mod pack instead.

StarkRG commented 2 years ago

I had this problem as well, I now only use GDLauncher to download new versions of the pack, then I copy it over to a multimc instance and run it from there. I haven't had a problem since.

I'm almost certain GDLauncher is at fault, not anything in the pack. Unfortunately MultiMC currently can't download curseforge packs, so you have to go the roundabout way to get it to work, but the pack does work.

ShiGhost commented 2 years ago

I also don't run the game under Linux via GDLauncher. Departures appear from AOF5 version 2.0.0 and higher.

TheRealKANi commented 2 years ago

New update - I went thru disabling all mods and trying step by step enabling some mods a couple at once. Game launches with no added mods, I added more and more untill 4 remaning, still it launched, but when I added one of the last four, it started crashing, that should have been easy to fix, but nope.. I took out all mods again and added only the last four, it started up.. I then reenabled all mods, and what do you know, the entire modpack just suddenly started up perfectly.. No crashes this first time for me. FYI my desktop "only" has 8GB of DDR4, and when testing my consumption was around ~90% of my total of 8, but I had 5144 MB assigned to AOF5 instance. I suspect lack of memory could be my issue. My quick test singleplayer session went without a hitch thou... On a final note. I will test again today with no changes to mods to see if just works now. Adding update later regarding the names of the four mods I was wrestling with.

TheRealKANi commented 2 years ago

I also don't run the game under Linux via GDLauncher. Departures appear from AOF5 version 2.0.0 and higher.

Aggreed, went thru 2.0.0 to 2.0.5 in my testings.

ghost commented 2 years ago

New update - I went thru disabling all mods and trying step by step enabling some mods a couple at once. Game launches with no added mods, I added more and more untill 4 remaning, still it launched, but when I added one of the last four, it started crashing, that should have been easy to fix, but nope.. I took out all mods again and added only the last four, it started up.. I then reenabled all mods, and what do you know, the entire modpack just suddenly started up perfectly.. No crashes this first time for me. FYI my desktop "only" has 8GB of DDR4, and when testing my consumption was around ~90% of my total of 8, but I had 5144 MB assigned to AOF5 instance. I suspect lack of memory could be my issue. My quick test singleplayer session went without a hitch thou... On a final note. I will test again today with no changes to mods to see if just works now. Adding update later regarding the names of the four mods I was wrestling with.

This is interesting. I also manually enbled and disalbed mods until it worked and I ended up disabling the following: goblin-traders, thonkutil, kubejs-create, kubejs, kjsextras, slight-gui-modifications. As soon as I have time again, I'll try and check if it also works on my maschine by just enabling those four mods and then enabling everything. Would be interesting to know why exactly that would work tho

TheRealKANi commented 2 years ago

Kubejs and slight-gui-modifications also popped up on my radar.. but could not figure out what to do about it.. anyone knows those mods better and possible where to go from here..

TheRealKANi commented 2 years ago

Btw.. tested minecrafts own launcher, ATLauncher, GD Launcher and MultiMC.. same error.. I also tryed with a ram upgrade from crutial 8 gb DDR 4 ~2100 MHz to kingston 16 gb DDR4 3200 mhz to eliminate the jvm half memory warning from all the launchers.. sems like no config change to jvm is going to help as of now.. and my kids winsucks machines runs the pack just fine.. No changes in std config.. Just works..

StarkRG commented 2 years ago

Even though I've definitely been able to intermittently run the 2.0.5 version of the pack with Sodium, Reese's Sodium Options, and Indium, it seems like removing them allows the pack to boot every time (or, at least, so far). From where I sit, it seems like some combination of those mods and at least one or two others is exposing a bug in the Nvidia driver. If anyone's having this problem with non-Nvidia graphics, though, then that's out the window.

EDIT: Well, scratch that, after running for a while it crashed and now won't start again. Second edit: and now I've enabled them and it works again. I hate this bug.

irunatbullets commented 2 years ago

I'm having this issue too using Zorin OS.

Do you know which Nvidia driver you're using?

I recently updated my Nvidia driver to 515, so I'm going to try rolling back.

crysthala commented 2 years ago

hs_err_pid9243.log latest.log

Hardware and stuff:

PrismMC (using 5.1) lets you use native GLFW in the Workaround tab of Settings, so I did that. Version 3.2.1-1 is installed on my system. Still crashes, but with a fascinating new error message and no hs_err_pid or crash report. latest.log

So then I installed libwjgl 2.9.3+dfsg1. Not sure if it changed anything. latest.log

Phew. This looks like a really cool pack, and I'd like to try it. Please let me know if you'd like me to poke and/or prod anything else :3

TheRealKANi commented 2 years ago

Okay.. this is getting to be a real issue for us linux people.. its the same error Im getting no matter what I do.. Loading Client.properties.. then nothing.. We need to get a mod/dev to look at this..

crysthala commented 2 years ago

Well, after enabling and disabling a whole bunch of mods, for no apparent reason, it started up. Could this be a load order thing somehow? E.g. Fabric does a mixin it should skip from a mod loading early, then skips a mixin it should do from a mod loading too late, and then everything breaks? I have only the vaguest ideas how mixins and load order for MC mods work, though. Just wild speculation. Anyway, here's a log from my (now running, yay!) game. Start up, change keybinds, create world.

latest.log

ETA: And here's a crash, trying to look up a recipe. Don't know if it's relevant, but just in case. crash-2022-11-07_08.54.27-client.txt

StarkRG commented 2 years ago

While trying to load the pack today, I tried all my little rituals that seemed to get it to boot before (launching nvidia settings, making sure Spectacle (KDE's screenshot program), etc.), I stumbled across a suggestion to reduce the amount of RAM back to the default 2GB. I decided just to try 4GB and it worked (I'd set my default to 8GB due to some very large Forge packs I'd been playing). Granted, this is just a single success, but it is, at least, something for other people to try.

crysthala commented 2 years ago

Set my LWJGL version to 3.3.1 and it started up. Here's the latest.log of it getting to the main menu. latest.log

Naturally, I was so excited that I immediately closed the game, then tried to open it again. No changes. It went differently. Here's some logs. (No hs_err_pid was generated, as that only seems to happen when I tell PrismMC not to use the native LWJGL library.) latest.log crash-2022-11-07_16.55.29-client.txt

Anyone using the Nouveau drivers? I would test them, but they don't play nice with my machine at all.

crysthala commented 2 years ago

I keep seeing that "stack smashing detected" error when it fails to start. Apparently, that's something you get when a program detects a certain kind of buffer overflow that can be used in security exploits, which resulted in a bunch of emergency patches being put out a few years ago. It it possible for a Minecraft mod to mixin so hard it accidentally triggers an antimalware feature?

lazurit11 commented 2 years ago

Just wanted to add that my Intel iGPU has the issue as well.

w3ricardo commented 2 years ago

For me, versions 2.0.5 and versions 2.0.6 don't load on Ubuntu, version 2.0.4 works fine. All work fine on Windows. Partial log: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f97d541674b, pid=12075, tid=12076 # # JRE version: OpenJDK Runtime Environment Microsoft-28056 (17.0.1+12) (build 17.0.1+12-LTS) # Java VM: OpenJDK 64-Bit Server VM Microsoft-28056 (17.0.1+12-LTS, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64) # Problematic frame: # C [libglfw.so+0x1674b] Edit: saw a Java update today, will check if it makes a difference

crysthala commented 2 years ago

After toying with the mod list and the settings, it seems to launch every time now. Still running on Prism Launcher 5.1, using native GLFW, Zulu JDK 17.0.4.1, LWJGL 3.3.1, Fabric Loader 0.14.10.

Added:

Disabled, mostly because I don't play online or I suspected they were causing issues:

Other stuff:

Random observations:

JohnnyIrvin commented 2 years ago

I'm on Ubuntu 22. Unable to run 2.0.5 or 2.0.6 without disabling ThonkUtil and Goblin Traders

ajkros commented 2 years ago

Im on Manjaro KDE Plasma 5.26.3 running Java 19.0.1 and Im having the same launch and crash issue.

Edit: Modpack version 2.0.6

Report: hs_err_pid141117.log

TheRealKANi commented 2 years ago

Im on Manjaro KDE Plasma 5.26.3 running Java 19.0.1 and Im having the same launch and crash issue.

Edit: Modpack version 2.0.6

Report: hs_err_pid141117.log

I can see from the logs that you are running AMD cpu, any chance you are using nvidia gpu? AFAIK the error/bug/issue is present only on nvidia/intel GPU's using Linux

ajkros commented 2 years ago

Im on Manjaro KDE Plasma 5.26.3 running Java 19.0.1 and Im having the same launch and crash issue. Edit: Modpack version 2.0.6 Report: hs_err_pid141117.log

I can see from the logs that you are running AMD cpu, any chance you are using nvidia gpu? AFAIK the error/bug/issue is present only on nvidia/intel GPU's using Linux

Nope, Radeon RX 5700 XT

Minionflo commented 2 years ago

Just more logs: https://paste.ee/p/Qxw9l I know that im trying to run AOF6 but i think its the same error as here

fluse1367 commented 2 years ago

Well, after enabling and disabling a whole bunch of mods, for no apparent reason, it started up. Could this be a load order thing somehow? E.g. Fabric does a mixin it should skip from a mod loading early, then skips a mixin it should do from a mod loading too late, and then everything breaks? I have only the vaguest ideas how mixins and load order for MC mods work, though. Just wild speculation. Anyway, here's a log from my (now running, yay!) game. Start up, change keybinds, create world.

latest.log

ETA: And here's a crash, trying to look up a recipe. Don't know if it's relevant, but just in case. crash-2022-11-07_08.54.27-client.txt

I have observed the exact same behavior on a different modpack (Dreamcraft) with PrismLauncher 5.2 (flatpak).

I was able to solve that stuff by using LWJGL 3.2.2, selecting the "use system glfw installation" workaround and copying the libglfw native library into the jdk lib directory:

sudo cp /usr/lib64/libglfw.so.3.3 /var/lib/flatpak/app/org.prismlauncher.PrismLauncher/current/active/files/jdk/17/lib/libglfw.so
r-vd-woude commented 2 years ago

Thank you so much! This solve my issue with both this pack and with Dreamcraft.

ramidzkh commented 1 year ago

+1 for @fluse1367, looks like replacing libglfw with one compiled from source also works

gumgum7134 commented 1 year ago

+1 for @fluse1367, looks like replacing libglfw with one compiled from source also works

I tried this and it didn't work but it gave me a new error GLFW error 65540: Invalid scancode -1. Absolutely 0 clue what scan codes have to do with it but i did notice that on the occasions i got it to run i had to fix a couple weird keybinding issues

gumgum7134 commented 1 year ago

So I toyed around with this some more and it turns out it's a weird keybinding issue. Specifically, I had unmapped the Chisel & Bits reset measuring tape key from right click because it was causing a conflict not letting me right click anyway. If I go into options.txt and remap it to right click minecraft will finally boot consistently. It also works just remapping it to anything else as long as it's mapped.

database64128 commented 1 year ago

Not sure if it's related, but everyone who has encountered this issue seems to be running KDE. I'm also on Arch but I use GNOME and I've never had this issue with any of the modpacks I've played. I use PrismLauncher from AUR with default GLFW settings, so the game's running in Xwayland. I don't even have the glfw-* packages installed on my system. I don't have a dGPU, so it's just i9-13900K and its iGPU.

Minionflo commented 1 year ago

i have the problem with GNOME and Ubuntu

CeledonianError commented 1 year ago

Glad to see I'm not the only one having issues. I'm also on GNOME. Crash is identical to the one that started this thread. Disabling most of the mods that @crysthala listed seems to have fixed it. I've since added Diggus Maximus and it appears to be okay.

Disabled mods:

Specs: Linux Mint 20.3 Cinnamon 5.2.7 Kernel 5.15.0-52-generic Core i5-9300H GTX 1650 Mobile, proprietary drivers: 515.65.01 16 GB of RAM, 6 GiB allocated to AOF 5

ramidzkh commented 1 year ago

+1 for @fluse1367, looks like replacing libglfw with one compiled from source also works

I tried this and it didn't work but it gave me a new error GLFW error 65540: Invalid scancode -1. Absolutely 0 clue what scan codes have to do with it but i did notice that on the occasions i got it to run i had to fix a couple weird keybinding issues

https://github.com/MinecraftMachina/ManyMC/issues/76#issuecomment-1196620387

sed -i 's/key.keyboard.unknown/key.keyboard.f13/g' options.txt fixed it for me

crysthala commented 1 year ago

I have observed the exact same behavior on a different modpack (Dreamcraft) with PrismLauncher 5.2 (flatpak).

I was able to solve that stuff by using LWJGL 3.2.2, selecting the "use system glfw installation" workaround and copying the libglfw native library into the jdk lib directory:

sudo cp /usr/lib64/libglfw.so.3.3 /var/lib/flatpak/app/org.prismlauncher.PrismLauncher/current/active/files/jdk/17/lib/libglfw.so

A variant of this has worked for me. My file system is structured differently and I'm not using the same libglfw version, so the command as written didn't work.

If you go to /usr/ and search for libglfw, one (or more?) result should be libglfw.so.#.#. Mine turned out to be libglfw.so.3.2 in /usr/lib/x86_64-linux-gnu, but yours might be different. Copy and paste that into the folder specified above if you're using Prism Launcher (or one of its relatives). I don't know what you'd do if you use the vanilla launcher or something else, though.

Maybe Linux is directing programs to libraries in a way Fabric and/or certain mods aren't able to handle? Don't know. But I do know that I haven't had this issue since copying that library over. Thank you very much, @fluse1367!

CeledonianError commented 1 year ago

+1 for @fluse1367, looks like replacing libglfw with one compiled from source also works

I tried this and it didn't work but it gave me a new error GLFW error 65540: Invalid scancode -1. Absolutely 0 clue what scan codes have to do with it but i did notice that on the occasions i got it to run i had to fix a couple weird keybinding issues

MinecraftMachina/ManyMC#76 (comment)

sed -i 's/key.keyboard.unknown/key.keyboard.f13/g' options.txt fixed it for me

Despite it working last night, it stopped working today. Just ran this command and it's running fine again. Hopefully this fix sticks, lol. Tysm!

Me from the future here: It did not stick.

fluse1367 commented 1 year ago

I have observed the exact same behavior on a different modpack (Dreamcraft) with PrismLauncher 5.2 (flatpak). I was able to solve that stuff by using LWJGL 3.2.2, selecting the "use system glfw installation" workaround and copying the libglfw native library into the jdk lib directory:

sudo cp /usr/lib64/libglfw.so.3.3 /var/lib/flatpak/app/org.prismlauncher.PrismLauncher/current/active/files/jdk/17/lib/libglfw.so

A variant of this has worked for me. My file system is structured differently and I'm not using the same libglfw version, so the command as written didn't work.

If you go to /usr/ and search for libglfw, one (or more?) result should be libglfw.so.#.#. Mine turned out to be libglfw.so.3.2 in /usr/lib/x86_64-linux-gnu, but yours might be different. Copy and paste that into the folder specified above if you're using Prism Launcher (or one of its relatives). I don't know what you'd do if you use the vanilla launcher or something else, though.

Maybe Linux is directing programs to libraries in a way Fabric and/or certain mods aren't able to handle? Don't know. But I do know that I haven't had this issue since copying that library over. Thank you very much, @fluse1367!

It’s actually not because of Fabric or linux itself, that the bundled JDK cannot find the native library, it’s because of the flatpak sandboxing (at least that’s my only explanation why you have to copy the library manually).

gumgum7134 commented 1 year ago

I have observed the exact same behavior on a different modpack (Dreamcraft) with PrismLauncher 5.2 (flatpak). I was able to solve that stuff by using LWJGL 3.2.2, selecting the "use system glfw installation" workaround and copying the libglfw native library into the jdk lib directory:

sudo cp /usr/lib64/libglfw.so.3.3 /var/lib/flatpak/app/org.prismlauncher.PrismLauncher/current/active/files/jdk/17/lib/libglfw.so

A variant of this has worked for me. My file system is structured differently and I'm not using the same libglfw version, so the command as written didn't work. If you go to /usr/ and search for libglfw, one (or more?) result should be libglfw.so.#.#. Mine turned out to be libglfw.so.3.2 in /usr/lib/x86_64-linux-gnu, but yours might be different. Copy and paste that into the folder specified above if you're using Prism Launcher (or one of its relatives). I don't know what you'd do if you use the vanilla launcher or something else, though. Maybe Linux is directing programs to libraries in a way Fabric and/or certain mods aren't able to handle? Don't know. But I do know that I haven't had this issue since copying that library over. Thank you very much, @fluse1367!

It’s actually not because of Fabric or linux itself, that the bundled JDK cannot find the native library, it’s because of the flatpak sandboxing (at least that’s my only explanation why you have to copy the library manually).

it's not just a flatpak issue it happens on the native version as well and the same solution works

bendem commented 1 year ago

I have looked at the src rpm for glfw in fedora and there are no patches applied, it's pure upstream software. My guess is compilation versions/options are somewhat different though, causing the issue.

Seegras commented 1 year ago

Started with -Dorg.lwjgl.glfw.libname=/usr/lib/x86_64-linux-gnu/libglfw.so.3.3 as Java argument, and it started throwing "GLFW error 65540: Invalid scancode -1"; which I could fix by setting all occurences of key.keyboard.unknown in options.txt to a defined key.

See also: https://github.com/MinecraftMachina/ManyMC/issues/76

Astralchroma commented 1 year ago

https://github.com/LWJGL/lwjgl3/issues/822 https://github.com/glfw/glfw/pull/2024

Seegras commented 1 year ago

Can be closed. AoF6 offers about the same, without the problem.

Linguardium commented 1 year ago

the problem also happens on aof6, because its a system issue not a pack issue. you can review the support thread channel on the discord if you are skeptical

Seegras commented 1 year ago

Now AoF6 has the same problem, apparently since 1.4.2. https://github.com/TeamAOF/All-of-Fabric-6/issues/115

Arr4y commented 1 year ago

Hi, running Garuda Linux here (Arch) and I ran into the same issue where it crashes immediately.

I took a look at the core dump and this section is what I looked at. ` A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x00007f82f981674b, pid=201761, tid=201762

JRE version: OpenJDK Runtime Environment (17.0.7+7) (build 17.0.7+7) Java VM: OpenJDK 64-Bit Server VM (17.0.7+7, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64) Problematic frame: C [libglfw.so+0x1674b] `

Where this part specifically stuck out to me. Problematic frame: C [libglfw.so+0x1674b]

I am running Prism Launcher. I decided to enable the "Use system installation of GLFW" in the native libraries section in the settings of the instance. I thought maybe forcing Minecraft to use Linux's native GLFW library would change something. And so it did.

After this change, AOF5 (I haven't tested it for AOF6) started working with no issues starting up anymore. Maybe the library used is what caused this?

Packman28334 commented 1 year ago

Same issue. AMD Ryzen 5 5600G, AMD Radeon RX 6650 XT, 32GB DDR4 RAM (16GB allocated), Linux Mint 21.1 Vera, pack version 2.0.6 on PrismLauncher.

I compiled GLFW 3.3.8 and installed via 'sudo make install.'

I have the same file structure as crysthala:

If you go to /usr/ and search for libglfw, one (or more?) result should be libglfw.so.#.#. Mine turned out to be libglfw.so.3.2 in /usr/lib/x86_64-linux-gnu, but yours might be different. Copy and paste that into the folder specified above if you're using Prism Launcher (or one of its relatives). I don't know what you'd do if you use the vanilla launcher or something else, though.

I am using the AppImage of PrismLauncher. I pointed Prism to the system GLFW install, and set "-Dorg.lwjgl.glfw.libname=/usr/lib/x86_64-linux-gnu/libglfw.so.3.3" in Java arguments (and yes, this is where it is installed). Game still crashes when trying to launch, right when the Minecraft window opens.

Here is the end of the log file: [17:11:01] [Render thread/INFO]: Backend library: LWJGL version 3.2.2 build 10 [17:11:01] [Render thread/INFO]: Loaded client.properties buffer overflow detected : terminated Process crashed with exitcode 6.

I initially used the Flatpak, but even after copying the libglfw.so to the Flatpak, the game wouldn't run.

EDIT: Reinstalled the Flatpak, the error persists. Same error message as the AppImage: [12:40:44] [Render thread/INFO]: Backend library: LWJGL version 3.2.2 build 10 [12:40:44] [Render thread/INFO]: Loaded client.properties buffer overflow detected : terminated Process crashed with exitcode 6.

EDIT 2: I now have the game launching consistently! Uninstall Sodium, Iris, and Indium. Have the "System GLFW" workaround turned off. I did have the libglfw.so file copied, but I don't know if that makes a difference.

Arr4y commented 1 year ago

Same issue. AMD Ryzen 5 5600G, AMD Radeon RX 6650 XT, 32GB DDR4 RAM (16GB allocated), Linux Mint 21.1 Vera, pack version 2.0.6 on PrismLauncher.

I compiled GLFW 3.3.8 and installed via 'sudo make install.'

I have the same file structure as crysthala:

If you go to /usr/ and search for libglfw, one (or more?) result should be libglfw.so.#.#. Mine turned out to be libglfw.so.3.2 in /usr/lib/x86_64-linux-gnu, but yours might be different. Copy and paste that into the folder specified above if you're using Prism Launcher (or one of its relatives). I don't know what you'd do if you use the vanilla launcher or something else, though.

I am using the AppImage of PrismLauncher. I pointed Prism to the system GLFW install, and set "-Dorg.lwjgl.glfw.libname=/usr/lib/x86_64-linux-gnu/libglfw.so.3.3" in Java arguments (and yes, this is where it is installed). Game still crashes when trying to launch, right when the Minecraft window opens.

Here is the end of the log file: [17:11:01] [Render thread/INFO]: Backend library: LWJGL version 3.2.2 build 10 [17:11:01] [Render thread/INFO]: Loaded client.properties buffer overflow detected : terminated Process crashed with exitcode 6.

I initially used the Flatpak, but even after copying the libglfw.so to the Flatpak, the game wouldn't run.

EDIT: Reinstalled the Flatpak, the error persists. Same error message as the AppImage: [12:40:44] [Render thread/INFO]: Backend library: LWJGL version 3.2.2 build 10 [12:40:44] [Render thread/INFO]: Loaded client.properties buffer overflow detected : terminated Process crashed with exitcode 6.

EDIT 2: I now have the game launching consistently! Uninstall Sodium, Iris, and Indium. Have the "System GLFW" workaround turned off. I did copy the libglfw.so file copied, but I don't know if that makes a difference.

My problem had something to do with not having "use system GLFW" on. I turned it on and it was what had fixed all my problems. GLFW is pre-installed in my system but can be installed via pacman (apt-get in your case of Linux Mint). I did not have to point it to the .so file, I only enabled it and did not touch anything else. After I did that everything was working without any issue.

You could try installing GLFW (I believe it's under the name of glfw3) via "apt-get" then reboot your system. After that enable the "Use system installation of GLFW" and see if it works.