#AoF 5 segfaults in LWJGL on launch (Linux)

47 messages · Page 1 of 1 (latest)

sudden storm
#

Basically. Arch Linux, nvidia, X11 (was gnome-shell+paperwm, now just using openbox, didn't help either way.) The game would crash seemingly with no explanation before any graphics were displayed, it did open a window briefly but it never drew into it.

Modpack version: 2.0.4. Fabric Loader version is 0.14.9-1.18.2
Messages like this found in /.../hs_err_pid<SOME-PROCESS-ID>.log. The pack was downloaded through PrismMC, but I'm using the minecraft launcher to start it, out of paranoia.

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f9b30c1674b, pid=390241, tid=390243
#
# 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]

I saw a "lwjgl patched for minecraft" in the AUR while I was installing stuff but it was wayland-specific so I assume not relevant here.

1.18.2 by itself works fine. The Fabric Loader with no mods also loads fine.

I'm completely out of ideas. Help? :(

#

Also idk how to not tag it 'recipe' sorry

drowsy charm
#

Sounds like a graphics driver problem. I'm thinking that sodium and/or iris might be using feature's that not used in Vanilla Minecraft.

#

Are you running the proprietary drivers?

sudden storm
#

I should be, yeah. It looks like I just launched the 'vanilla' game with only sodium, but I'll add Iris and see what happens, that was my only remaining idea (okay, maybe I had one idea left.)

drowsy charm
#

^^ I do love Arch but Arch + Nvidia can cause some headache's

sudden storm
#

pretty much every way i've had my computer set up in the past year has had at least one rather noticeable downside <.< including when i was using windows

#

ugh, iris and sodium on their own ALSO load. ._.

drowsy charm
#

Damn...

sudden storm
#

...I think it may've been create. I disabled these and got a progress bar

cccbridge-1.2.0-fabric.jar.disabled           kubejs-create-fabric-1802.2.2-build.28.jar.disabled
create-fabric-1.18.2-0.5.0e-733.jar.disabled  megane-7.9.0.jar.disabled
createplus-1.0.0-beta4.jar.disabled
drowsy charm
#

Hum, might still be related to graphics then I guess

sudden storm
#

Yeah, this seems to consistently load to the menu. And yeah I assume its a graphics crash due to the crash happening in LWJGL <.< I think the complete log with all the hex codes and stuff also mentioned nvidia somewhere in there.

drowsy charm
#

Have you installed nvidia-dkms and nvidia-utils?

#

Did you also install indium when testing sodium and iris?

sudden storm
#

nvidia-lts rather than -dkms bc i used linux-lts bc my brain was like "it might be more stable" <.< nvidia-utils yes though. installing indium i will try

drowsy charm
#

Are you running lts kernel?

#

Might not be an issue but I've had problems with driver and kernel incompatibilities before

#

If not on lts kernel I would go with nvidia-dkms instead

sudden storm
#

yeah. linux-lts. ...pretty sure. i had to think about it bc i'm doing zfs and the versions have to match for it to build/work

drowsy charm
#

Okay

sudden storm
#

new fun twist: create by itself (well, by itself w/sodium/indium/etcetera) loads fine

#

even weirder: it seems to work with CreatePlus and megane disabled
at least to the point of showing the loading screen/splash/progressbar and eventually, menu. i'd keep poking it to see if i could load a world but it is silly late and i have a class in the morning so i'm going to bed -.-

#

i have no idea how i arrived at this configuration. maybe modded minecraft is just cursed

#

(well, technically, i arrived at this configuration by disabling create, finding some mods to depend on it, disabling those as well, and then eventually i was tinkering with that subset, because create itself loaded fine outside of the modpack itself sooo)

drowsy charm
#

That's just weird...

#

Goodnight

hollow copper
#

I have a problem very similar to this one, but I have an AMD card and I'm using the Mesa-git drivers.

#

I got around this by disabling Megane.

half hinge
#

Hi got the same issue (Arch Linux - Wayland), also using AMD Cards. First i installed glfw-wayland package and then told Prism Launcher to use my system glfw library. Sometimes i got the segfault, in theses cases i just close prism launcher relaunch it and relaunch AOF5. It's annoying but consistent fortunately

half hinge
#

Update: i'm now unable to play AOF5 anymore. Using the system glfw (with glfw-wayland package) will return me an "GLFW error 65540: Wayland: Invalid scan -1" and using the LGLFW 3.2.2 from Prism Launcher will have 1/32 chances of launching the game. And anyway even if the game launch, every two hours my entire pc crash. Certainly cause by JVM taking too much memory.

tall brook
#

I'm having the same issue, Arch, AMD, X11
weirdly enough, 2.0.4 loads fine, my issue manifests with 2.0.5 only
considering it worked until a few days ago, I must assume it has something to do with the system update I did recently

hollow copper
#

IDK about the thread mentioning that it is a GDLauncher issue. The segfault happens to me sometimes on Prism Launcher.

#

So I believe my situation is related.

whole jetty
vestal charm
#

that's such a bizarre fix

whole jetty
#

any key would've worked; i just never use F12

#

but yeah, computers are evil

viscid thunder
#

any updates?

fading hill
fading hill
acoustic pilot
#

I am wondering if the ATLauncher setting for "use system GLFW" would alleviate some of those steps (like the deleting and linking portion)

fading hill
#

It could, yes, since technically this is what we are doing here

#

However, I'm not sure people will be willing to switch launcher for that

acoustic pilot
#

i mean, its also a good launcher 😛 but I get that. having someone remove libraries from their natives folder and create links is probably easier to sell.

queen thistle
#

Sorry to necro the thread here, just wanted to add my 2 cents that I was encountering the segfault issue trying to run aof5 on steam deck (Arch-based, AMD APU) with prism launcher, and disabling megane fixed the issue

half hinge