Modpack Config Checker causes java error on linux

[fbfnysnshnsgnwg]

When launching meatballcraft, this java error happens
hs_err_pid18790.log
Easily fixed, just remove the mod.
What I want is either a fix or just removal of the mod.
All I know about the error is that it is related to the code that the mod uses to open a popup window

[sainagh]

The mod is used because most users forget to change their RAM allocation for the pack. There is some ongoing work to reduce some of the RAM requirements by default, but at the moment preventing issues with RAM allocation is more important so the mod will stay in.

The frequency of the crash is currently being polled, and if it turns out the issue is frequent, it will be addressed.

[fbfnysnshnsgnwg]

It might be a linux issue

[TheRealGorrik]

I am experiencing this issue as well on Linux Mint using GDLauncher.
During the initial boot up after installing the pack, it runs fine. On the second boot up, it crashes with the issue described during startup.

Is there a config file or cache that could be safely deleted and regenerated on start up that might be a quick fix for this issue?

[fbfnysnshnsgnwg]

@TheRealGorrik well it must be a linux mint/ubuntu issue

[TheRealGorrik]

@TheRealGorrik well it must be a linux mint/ubuntu issue

I agree that the issue is probably unique to the Linux environment from what I can see from the discord and this post. Given that the game ran fine for me the very first time running after install, then fails to run after that, it indicates that some file generated during the first run is in an invalid state. A quick solution would be to identify the problem file and delete it and let it regenerate on startup until an actual solution is found for it.

[TheRealGorrik]

So based on the response by @sainagh, I reinstalled the pack through GDLauncher and set my memory allocation to a non-default amount before launching the pack. After that I unlocked the mod pack in the overview panel, I went to the mods tab and disabled the modpack configuration checker mod. I successfully launched the pack twice after that, which is better than before. The only issue was when I connected to my server, the service mod list was not in-sync with mine. Disabling it on the server seemed to have worked for now. Probably not the best way of handling it, but I am able to play now.

[bstock84]

Just for some additional data points, I'm not seeing this error and running on linux. Both a desktop and laptop launch fine.

OS: Manjaro
DE: KDE Plasma
Launcher: FTB Launcher (AppImage version)

I have FTB set to use 8GB by default on both systems.

[fbfnysnshnsgnwg]

@bstock84 i wonder if it has to do with cinnamon (i use linux mint @TheRealGorrik as well)

[bstock84]

@fbfnysnshnsgnwg @TheRealGorrik

I tested on Manjaro by setting FTB laucnher to use 4GB ram:

KDE Plasma (wayland)- fine
KDE Plasma (X11) - fine
Cinnamon (X11)- fine
Cinnamon (wayland) - fine

Testing again, still on Manjaro with GDLauncher, instance set to 4GB ram in the following DE's:

KDE Plasma (wayland)- fine
KDE Plasma (X11) - fine
Cinnamon (X11)- fine
Cinnamon (wayland) - fine

Both launchers are using their recommend java version that comes along with the install.

I had an ubuntu VM so I tried GDLauncher on it with both of the following:

Gnome (default) - fine
Cinnamon (X11) - fine

Then I figured while I'm at it, let's see if I can reproduce. I installed Mint on a VM, setup GDLauncher, installed the pack and tried to run (with its default setting of 4GB), and observed the following:

• Tried to launch with Cinnamon (X11) as that's the default, and the error popped up as expected
• Changed ram in GDLauncher to 8GB and game fully loaded first time. Started a single player map, then exited the game.
• Ran the game again with it still set to 8GB but game still ran fine
• Lowered the ram back to 4GB and lauched the game, popup came up but clicked continue, game still attempted to run but I killed it after an hour... it didn't crash though
• Force closed and restarted the game, popup still came up ok

So I'm unable to reproduce this in a VM. It seems a strange issue, since Java should have all it needs with it for its window decorating stuff. Since you're able to get the game to load and run ok, it sounds like base system stuff is all fine too. I did all this testing on my laptop which has a Ryzen 7 7840U w/ on-cpu Radeon 780M graphics. My desktop is a Ryzen CPU with discrete AMD GPU. I wonder if users affected by this bug are all on nVidia or intel GPU. Maybe you could try gnome/kde/xfce or something and see if you get the same issue? Or try FTB Launcher perhaps?

Also if you set your memory to above the recommended amount of memory, do you still get a crash? Since the popup window shouldn't come up in that case I'd expect the game not to crash if the issue is somewhere in the code used for the popup.

[fbfnysnshnsgnwg]

@bstock84 I had a similar issue with antimatter chemistry, and made an issue in their repo, and someone told me that my kernel driver was old (5.15.0), so it might be a kernel issue
oh also I use a Ryzen 9 7900x and RTX 3060

[fbfnysnshnsgnwg]

update: i did some digging, and it seems to be a problem with java.awt (i had this issue AGAIN on sevtech this time)
j java.awt.Toolkit.getDesktopProperty(Ljava/lang/String;)Ljava/lang/Object;+32
j javax.swing.JFileChooser.installShowFilesListener()V+7
j javax.swing.JFileChooser.setup(Ljavax/swing/filechooser/FileSystemView;)V+1
j javax.swing.JFileChooser.(Ljava/io/File;Ljavax/swing/filechooser/FileSystemView;)V+123
j javax.swing.JFileChooser.()V+9
lines from sevtech log ^

j java.awt.Toolkit.getDesktopProperty(Ljava/lang/String;)Ljava/lang/Object;+32
j sun.swing.SwingUtilities2$AATextInfo.getAATextInfo(Z)Lsun/swing/SwingUtilities2$AATextInfo;+11
j javax.swing.plaf.metal.MetalLookAndFeel.initComponentDefaults(Ljavax/swing/UIDefaults;)V+12062
j javax.swing.plaf.basic.BasicLookAndFeel.getDefaults()Ljavax/swing/UIDefaults;+25
j javax.swing.plaf.metal.MetalLookAndFeel.getDefaults()Ljavax/swing/UIDefaults;+9
j javax.swing.UIManager.setLookAndFeel(Ljavax/swing/LookAndFeel;)V+79
lines from meatball log ^

[bstock84]

update: i did some digging, and it seems to be a problem with java.awt (i had this issue AGAIN on sevtech this time)

Have you updated your system to latest, and are you still running kernel 5.15? If so you might want to try a dist upgrade so you're at least on a 6.x kernel to see if that helps.