Sign in to follow this  
Ramilan

Client won't launch after superhorse fix

Recommended Posts

I have the same issue.

...

OS: Linux
Running client version 4.1.134(b23e12c)

...

LWJGL version: 3.2.3 1.2.0
OpenGL vendor: NVIDIA Corporation
OpenGL renderer: GeForce GTX 670/PCIe/SSE2
OpenGL version: 4.6.0 NVIDIA 460.67

...

I started the Launcher in Debug-Mode.

 

On 5/27/2021 at 5:20 AM, adoll said:

~/download/wurm-launcher> ./WurmLauncher -c

 

It's run with Live - Old UI.

Share this post


Link to post
Share on other sites

/WurmLauncher -c isn't working for me, I get the same SIGSEGV error.  Using the debug client gives a bit more info:

~/download/wurm-launcher> ./WurmLauncher -c
Runtime path: /home/USER/download/wurm-launcher/linux64/runtime/lib/amd64/server/libjvm.so
Working Directory: /home/USER/download/wurm-launcher
Number of options: 10
Native libs: -Djava.library.path=/home/USER/download/wurm-launcher:/home/USER/download/wurm-launcher/jcef-natives:/home/USER/download/wurm-launcher/linux64/runtime/lib/amd64Create java VM!
java.library.path: /home/USER/download/wurm-launcher:/home/agd/download/wurm-launcher/jcef-natives:/home/USER/download/wurm-launcher/linux64/runtime/lib/amd64
java.class.path: /home/USER/download/wurm-launcher/client_live_-_debug.jar
sun.java.command:null
OS: Linux
[LWJGL] Version: 3.2.3 1.2.0
[LWJGL] 	 OS: Linux v5.12.4-2-default
[LWJGL] 	JRE: 1.8.0_211 amd64
[LWJGL] 	JVM: Java HotSpot(TM) 64-Bit Server VM v25.211-b12 by Oracle Corporation
[LWJGL] Loading JNI library: lwjgl
[LWJGL] 	Module: org.lwjgl
[LWJGL] 	Loaded from org.lwjgl.librarypath: /tmp/lwjglagd/3.2.3-1.2.0/liblwjgl.so
[LWJGL] Loading library: glfw
[LWJGL] 	Module: org.lwjgl.glfw
[LWJGL] 	Loaded from org.lwjgl.librarypath: /tmp/lwjglagd/3.2.3-1.2.0/libglfw.so

(WurmLauncher:29775): Gdk-CRITICAL **: 19:14:08.204: gdk_x11_display_set_window_scale: assertion 'GDK_IS_X11_DISPLAY (display)' failed
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f29469bcb2c, pid=29775, tid=0x00007f286011f640
#
# 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:
# C  [libX11.so.6+0x31b2c]  XInternAtom+0x3c
#
# Core dump written. Default location: /home/USER/download/wurm-launcher/core or core.29775
#
# An error report file with more information is saved as:
# /home/USER/download/wurm-launcher/hs_err_pid29775.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

I run a dual-monitor setup, wondering if the other folks who don't get the old-UI version to work have the same?

 

Share this post


Link to post
Share on other sites

More on this, downgrading to X.org from Wayland solves it.  Wurm regular client runs when booting to X.org.

Share this post


Link to post
Share on other sites

Just in to report that I had the same issue. Client crashed on start

 

# 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:
# C  [libX11.so.6+0x31b2c]  XInternAtom+0x3c

 

Using X.org rather than Wayland allowed the client to run.

Share this post


Link to post
Share on other sites

FWIW, you can bypass the assertion by launching wurm with 

GDK_BACKEND=x11

set.

 

The client is trying to figure out how to talk to the Xwayland server. If you have one (you probably do if you are using any consumer distribution), it may fall on its face because the server isn't behaving exactly like the client expects.

 

You can set that environment variable however you like, though I wouldn't recommend setting it for your entire session. Using Plasma, I just used the Menu Editor to create a new launcher with GDK_BACKEND=x11 prepended to the path to WurmLauncher

Edited by Batolemaeus
  • Like 1

Share this post


Link to post
Share on other sites
On 12/13/2021 at 1:58 PM, Batolemaeus said:

FWIW, you can bypass the assertion by launching wurm with 


GDK_BACKEND=x11

set.

 

The above (as "export GDK_BACKEND=X11") solved the "assertion 'GDK_IS_X11_DISPLAY (display)' failed" error for me. Thank you!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this