My Wurm Launcher failing to launch on pop OS

[LilTurel 5]

I tried to set up the Wurm Launcher on Pop OS 22.04 LTS and the initial set up went through but afterwards when i try to launch it doesn't launch and it drops an error file in the directory. If it helps this what the file said:

 

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f0ad66c2443, pid=10111, tid=0x00007f0adee36000
#
# JRE version: Java(TM) SE Runtime Environment (8.0_211-b12) (build 1.8.0_211-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.211-b12 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0x6c2443]  ThreadStateTransition::transition_from_native(JavaThread*, JavaThreadState) [clone .constprop.119]+0x13
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

Thanks for the help, not sure what to do!

[Batolemaeus 183]

Run WurmLauncher from a terminal and post its output. The jvm dying is bad, but it looks like a symptom of the real problem.

[LilTurel 5]

I appreciate the help, I'll post it ASAP. There is a specific way I should run it in the terminal? Simply entering WurmLauncher doesn't work. Enter the full path maybe instead? 

[Batolemaeus 183]

./WurmLauncher from the same directory or the full path, yes. It should spew a lot more useful information leading up to the crash.

[LilTurel 5]

Here is what i got back:

Quote

 

user@pop-os:~/Downloads/wurmlauncher/wurm-launcher$ ./WurmLauncher
Runtime path: /home/username/Downloads/wurmlauncher/wurm-launcher/linux64/runtime/lib/amd64/server/libjvm.so
Working Directory: /home/username/Downloads/wurmlauncher/wurm-launcher
Number of options: 10
Native libs: -Djava.library.path=/home/username/Downloads/wurmlauncher/wurm-launcher:/home/username/Downloads/wurmlauncher/wurm-launcher/jcef-natives:/home/username/Downloads/wurmlauncher/wurm-launcher/linux64/runtime/lib/amd64Create java VM!
java.library.path: /home/username/Downloads/wurmlauncher/wurm-launcher:/home/username/Downloads/wurmlauncher/wurm-launcher/jcef-natives:/home/username/Downloads/wurmlauncher/wurm-launcher/linux64/runtime/lib/amd64
java.class.path: /home/username/Downloads/wurmlauncher/wurm-launcher/client_live.jar
sun.java.command:null
OS: Linux
Time is Wed Feb 08 16:07:59 MST 2023
Running client version 4.2.76(929a850)

=== System information ===
Executing from /home/USERNAME/Downloads/wurmlauncher/wurm-launcher/
Operating system: Linux (arch: amd64, version: 6.0.12-76060006-generic)
Java version: 1.8.0_211 (Oracle Corporation) <http://java.oracle.com/>
Jvm version: 25.211-b12 (Oracle Corporation) [Java HotSpot(TM) 64-Bit Server VM]
Available CPUs: 12
Max memory: 3962MB

>>> Main thread exiting.

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007ff4ddec2443, pid=7214, tid=0x00007ff4e6ae4000
#
# JRE version: Java(TM) SE Runtime Environment (8.0_211-b12) (build 1.8.0_211-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.211-b12 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0x6c2443]  ThreadStateTransition::transition_from_native(JavaThread*, JavaThreadState) [clone .constprop.119]+0x13
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/username/Downloads/wurmlauncher/wurm-launcher/hs_err_pid7214.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp

 

 

 

[Batolemaeus 183]

Disappointing. Let's throw the kitchen sink at it. Try this:

 

_JAVA_OPTIONS="-Dprism.verbose=true" GDK_BACKEND=x11 ./WurmLauncher

[LilTurel 5]

here is the output for you.

Quote

 

Runtime path: /home/carlosmelendez/Downloads/wurmlauncher/wurm-launcher/linux64/runtime/lib/amd64/server/libjvm.so
Working Directory: /home/carlosmelendez/Downloads/wurmlauncher/wurm-launcher
Number of options: 10
Native libs: -Djava.library.path=/home/carlosmelendez/Downloads/wurmlauncher/wurm-launcher:/home/carlosmelendez/Downloads/wurmlauncher/wurm-launcher/jcef-natives:/home/carlosmelendez/Downloads/wurmlauncher/wurm-launcher/linux64/runtime/lib/amd64Create java VM!
Picked up _JAVA_OPTIONS: -Dprism.verbose=true
java.library.path: /home/carlosmelendez/Downloads/wurmlauncher/wurm-launcher:/home/carlosmelendez/Downloads/wurmlauncher/wurm-launcher/jcef-natives:/home/carlosmelendez/Downloads/wurmlauncher/wurm-launcher/linux64/runtime/lib/amd64
java.class.path: /home/carlosmelendez/Downloads/wurmlauncher/wurm-launcher/client_live.jar
sun.java.command:null
OS: Linux
Prism pipeline init order: es2 sw 
Using java-based Pisces rasterizer
Using dirty region optimizations
Not using texture mask for primitives
Not forcing power of 2 sizes for textures
Using hardware CLAMP_TO_ZERO mode
Opting in for HiDPI pixel scaling
Prism pipeline name = com.sun.prism.es2.ES2Pipeline
Loading ES2 native library ... prism_es2
    succeeded.
GLFactory using com.sun.prism.es2.X11GLFactory
(X) Got class = class com.sun.prism.es2.ES2Pipeline
Failed Graphics Hardware Qualifier check.
System GPU doesn't meet the es2 pipe requirement
GraphicsPipeline.createPipeline: error initializing pipeline com.sun.prism.es2.ES2Pipeline
*** Fallback to Prism SW pipeline
Prism pipeline name = com.sun.prism.sw.SWPipeline
(X) Got class = class com.sun.prism.sw.SWPipeline
Initialized prism pipeline: com.sun.prism.sw.SWPipeline
 vsync: true vpipe: false
Time is Thu Feb 09 15:50:17 MST 2023
Running client version 4.2.77(52f90ae)

=== System information ===
Executing from /home/USERNAME/Downloads/wurmlauncher/wurm-launcher/
Operating system: Linux (arch: amd64, version: 6.0.12-76060006-generic)
Java version: 1.8.0_211 (Oracle Corporation) <http://java.oracle.com/>
Jvm version: 25.211-b12 (Oracle Corporation) [Java HotSpot(TM) 64-Bit Server VM]
Available CPUs: 12
Max memory: 3962MB

>>> Main thread exiting.
java.io.IOException: Wrong JPEG library version: library is 80, caller expects 90
    at com.sun.javafx.iio.jpeg.JPEGImageLoader.initDecompressor(Native Method)
    at com.sun.javafx.iio.jpeg.JPEGImageLoader.<init>(JPEGImageLoader.java:185)
    at com.sun.javafx.iio.jpeg.JPEGImageLoaderFactory.createImageLoader(JPEGImageLoaderFactory.java:49)
    at com.sun.javafx.iio.ImageStorage.getLoaderBySignature(ImageStorage.java:419)
    at com.sun.javafx.iio.ImageStorage.loadAll(ImageStorage.java:266)
    at com.sun.javafx.tk.quantum.PrismImageLoader2.loadAll(PrismImageLoader2.java:142)
    at com.sun.javafx.tk.quantum.PrismImageLoader2.<init>(PrismImageLoader2.java:77)
    at com.sun.javafx.tk.quantum.QuantumToolkit.loadImage(QuantumToolkit.java:732)
    at javafx.scene.image.Image.loadImage(Image.java:1073)
    at javafx.scene.image.Image.initialize(Image.java:804)
    at javafx.scene.image.Image.<init>(Image.java:707)
    at com.wurmonline.client.launcherfx.WurmMain.FZOk5L6Gfy(SourceFile:3443)
    at com.sun.javafx.application.PlatformImpl.lambda$null$402(PlatformImpl.java:295)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sun.javafx.application.PlatformImpl.lambda$runLater$403(PlatformImpl.java:294)
    at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:95)
    at com.sun.glass.ui.gtk.GtkApplication._runLoop(Native Method)
    at com.sun.glass.ui.gtk.GtkApplication.lambda$null$208(GtkApplication.java:245)
    at java.lang.Thread.run(Thread.java:748)

 

 

[Batolemaeus 183]

I should've suspected it first.

 

 

 

Since Your OS is based on some Ubuntu version the workaround should apply verbatim.

 

Of course, the real solution is to not use dynamic linking, or at the very least supply all libraries in your launcher. That's a Wurm dev issue.

 

At the rate the Wurm launcher atrophies I should probably think of reviving my own launcher…

[LilTurel 5]

Thanks a ton! I'm going to give this solution a try and report back. Maybe someday the devs will remedy this issue. 

[Finnn 3,304]

what's the problem to update the jlib-whatever to newer one, stack have similar issue and solution with wiping old and updating to newer one.. whenever it's not important system library seems like harmless fix

also yes.. if it's possible it's good that it's now reported and maybe this could be listed as prerequisite or known issue for specific distribution/version(s)

[LilTurel 5]

Hey so update guys, it worked! so Wurm is running now, the only issue i have now is that i have a 9 frames (but stable). I have a 1660ti so maybe its running off of my integrated graphics? thanks for all the help so far guys, the initial issue is fixed at least.

[Batolemaeus 183]

Either that or you're running nouveau. Nvidia is always a garbage fire. `prime-run ./WurmLauncher` on modern hardware to force it to run on discrete graphics, iirc? There may even be a graphical way of doing it, I haven't used Nvidia to do anything but CUDA on a headless system in a decade now…

[LilTurel 5]

i'm going to search for a graphical option if i can, when i use prime run it says command not found

 

edit: so i am running nouveau i'm pretty sure. I cant install nvidia prime and prime commands don't work.

 

Edited February 11, 2023 by LilTurel

[Saroman 1,341]

Switching to the proprietary nvidia driver in the "Pop Shop" driver section should be pretty straightforward, might be worth a try?

[LilTurel 5]

Hey guys actually solved it. they have a setting on nvidia x server settings under PowerMizer that I changed from auto to max performance. that seems to have forced wurm to run on my gpu

 

Edited February 12, 2023 by LilTurel