Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wayland: 'GDK_IS_X11_DISPLAY (display)' failed #2279

Closed
fredfortier opened this issue Jan 17, 2019 · 5 comments · Fixed by #3630
Closed

Wayland: 'GDK_IS_X11_DISPLAY (display)' failed #2279

fredfortier opened this issue Jan 17, 2019 · 5 comments · Fixed by #3630
Labels

Comments

@fredfortier
Copy link

@fredfortier fredfortier commented Jan 17, 2019

I'm using Fedora 29 with Gnome and Wayland and a fractional screen resolution. I built the project from sources. I can run headless modules but get this error when starting the bisq-desktop. This seems to indicate that the app expects an X11 server but I'm not sure. If so, is there a way to build for Wayland.

(java:26713): Gdk-CRITICAL **: 11:35:39.602: 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=0x00007f9dc46ac42b, pid=26713, tid=26764
#
# JRE version: OpenJDK Runtime Environment (10.0.2+13) (build 10.0.2+13)
# Java VM: OpenJDK 64-Bit Server VM (10.0.2+13, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  [libX11.so.6+0x3142b]
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e" (or dumping to /home/fredfortier/Downloads/bisq-0.9.3/core.26713)
#
# An error report file with more information is saved as:
# /home/fredfortier/Downloads/bisq-0.9.3/hs_err_pid26713.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.
#
Aborted (core dumped)
@jmliz

This comment has been minimized.

Copy link

@jmliz jmliz commented Jan 18, 2019

getting this exact same error.

@freimair

This comment has been minimized.

Copy link
Member

@freimair freimair commented Jan 31, 2019

yes, I have stumbled over the issue as well. see bisq-network/roles#78 (comment) for reference.

not sure what we can do about that. sounds to me as if the jdk is at fault.

@3cola

This comment has been minimized.

Copy link

@3cola 3cola commented Feb 14, 2019

On manjaro gnome (Arch linux + gnome-wayland), I get the same error with the AUR package bisq (0.9.3-1) and the app crashes.
But with the AUR package bisq-bin (0.9.3-2), by executing the app from the terminal by typing bisq, I see that some errors are still there, but the app displays on the screen and is usable.

@freimair

This comment has been minimized.

Copy link
Member

@freimair freimair commented Mar 3, 2019

I found a proposed fix which has been rejected.

However, adding a -Djdk.gtk.version=2 to the VM arguments does the trick for me!

@freimair freimair mentioned this issue Mar 3, 2019
@ripcurlx

This comment has been minimized.

Copy link
Member

@ripcurlx ripcurlx commented Mar 6, 2019

Closing as complete based on #2279 (comment).

@ripcurlx ripcurlx closed this Mar 6, 2019
devinbileck added a commit to devinbileck/bisq that referenced this issue Nov 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.