As a workaround we should either detect before cryptomator is starting which display server is used (e.g. by a startupscript) or should use always the announced workaround with java -Djdk.gtk.version=2 ....
Copied from original issue: cryptomator/cryptomator#720
From @infeo on September 19, 2018 8:47
When we finally switch to JavaFX 11, we should be aware of the bug JavaFX exposes on linux systems using Wayland as display server (see https://github.com/javafxports/openjdk-jfx/blob/jfx-11/doc-files/release-notes-11.md#javafx-crashes-with-openjdk-11-on-ubuntu-1804-with-wayland).
As a workaround we should either detect before cryptomator is starting which display server is used (e.g. by a startupscript) or should use always the announced workaround with
java -Djdk.gtk.version=2 ...
.Copied from original issue: cryptomator/cryptomator#720