Front load LWJGL 3.3.2 or better.
There's a new pack out called Homestead by Toekimi: https://www.curseforge.com/minecraft/modpacks/homestead-cozy. For Linux systems with AMD architecture also running GPUs, whether onboard or discrete, that are also AMD, the pack refuses to launch.
Some sporadic launching behavior can be had by disabling elocindev's mods, but it's not reliable. Upgrading the Mesa driver to 25.2.26 is helpful but again sporadic. Upgrading the Linux kernel 6.14 is also helpful but again sporadic.
What is not sporadic is using the Prism Launcher.
Turns out, CF APP only allows lwjgl 3.3.1-snapshot to run; PrismLauncher loads lwjgl-3.3.2 in front as a priority above the 3.3.1-snapshot.
To the best of my knowledge, that is why this pack reliably launches in Prism and not so much in CF App.
It does make me wonder how many other pack devs are suffering from this.
It seems to me that relying on Mojang to provide that library is no longer sufficient; for the best all around user experience, it's time to front load a new LWJGL.
-
Guest
- Jan 21 2026
- Future consideration
Related ideas
I'll be posting a video showcasing this issue. Hopefully we can get more votes and comments.
Hi there!
I am part of the CozyCord Staff Team (which has created Homestead), and I am also requesting for this to fixed ASAP!
We have gotten multiple people submitting this very issue.
Kind regards,
Serimah
As the developer of Homestead, I can confirm this is a widespread issue. I've had over 100 players report this exact crash scenario, and after extensive testing with our community, we've identified a clear pattern: every single affected player was launching through the CurseForge App, and every single one was able to play perfectly fine on their first boot through Prism Launcher.
This analysis lines up with what we've been seeing. The LWJGL version discrepancy appears to be the root cause... Prism prioritizing 3.3.2 over the 3.3.1-snapshot that CF App locks you into makes all the difference for AMD GPU users on Linux.
It's frustrating because from a pack dev perspective, there's not much we can do about it on our end. We're at the mercy of the launcher's library handling, and telling players "just use a different launcher" isn't a great solution when CurseForge is where the pack is hosted and where most players discover it. We're even at the point of just simply not releasing on Curseforge any longer and prioritizing Modrinth only.
I'd love to see CF App address this, whether that's updating their bundled LWJGL or giving pack developers the option to specify library overrides. Until then, if you're on Linux with AMD hardware and running into startup crashes, Prism Launcher is unfortunately your best bet.
Same, I wonder how many of the packs that wouldn't launch I assumed were broken because of my system having amd with amd gpu on linux. this flaw makes the app look poor now that this is apparent.