Can not run on Fedora 29

os:linux

#1

Hi,

I am trying to run version 1.4.6 AppImage on a Fedora 29 and I get this error:

11:37:12.728 [main] DEBUG org.cryptomator.common.Environment - user.language: es
11:37:12.731 [main] DEBUG org.cryptomator.common.Environment - user.region: null
11:37:12.731 [main] DEBUG org.cryptomator.common.Environment - logback.configurationFile: null
11:37:12.731 [main] DEBUG org.cryptomator.common.Environment - cryptomator.settingsPath: ~/.config/Cryptomator/settings.json:~/.Cryptomator/settings.json
11:37:12.731 [main] DEBUG org.cryptomator.common.Environment - cryptomator.ipcPortPath: ~/.config/Cryptomator/ipcPort.bin:~/.Cryptomator/ipcPort.bin
11:37:12.731 [main] DEBUG org.cryptomator.common.Environment - cryptomator.keychainPath: null
11:37:12.731 [main] DEBUG org.cryptomator.common.Environment - cryptomator.logDir: ~/.local/share/Cryptomator/logs
11:37:12.731 [main] DEBUG org.cryptomator.common.Environment - cryptomator.mountPointsDir: ~/.local/share/Cryptomator/mnt
11:37:12.910 [main] DEBUG org.cryptomator.common.settings.SettingsProvider - Attempting to load settings from /home/juanje/.config/Cryptomator/settings.json
11:37:12.913 [main] DEBUG org.cryptomator.common.settings.SettingsProvider - Attempting to load settings from /home/juanje/.Cryptomator/settings.json
11:37:12.973 [main] INFO org.cryptomator.common.settings.SettingsProvider - Settings loaded from /home/juanje/.Cryptomator/settings.json
11:37:13.279 [main] INFO org.cryptomator.launcher.FileOpenRequestHandler - Unable to setOpenFileHandler, probably not supported on this OS.
11:37:13.295 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.4.6 on Linux 4.20.10-200.fc29.x86_64 (amd64)
11:37:13.396 [main] INFO  o.c.launcher.IpcProtocolImpl - Received launch args: -Djdk.gtk.version=2

(cryptomator-1.4.6-x86_64.AppImage:12195): Gdk-CRITICAL **: 11:37:13.578: 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=0x0000001800000018, pid=12195, tid=12245
#
# JRE version: OpenJDK Runtime Environment (11.0.2+9) (build 11.0.2+9)
# Java VM: OpenJDK 64-Bit Server VM (11.0.2+9, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  0x0000001800000018
#
# 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 /tmp/.mount_cryptoWVEy7O/app/core.12195)
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid12195.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' generado)

#2

There is a quite similiar issue already on the bug tracker: https://github.com/cryptomator/cryptomator/issues/846

But as i can see in the log, you already using the described workaround with -Djdk.gtk.version=2. :see_no_evil:

With the same instructions given in the github issue, you can add the option -Djdk.gtk.verbose=true and see what GTK version is used (2 or 3).

Otherwise, maybe the setting GDK backend to x11 described here can help.


#3

Nope. According to the log file -Djdk.gtk.version=2 has been passed as a program argument to Cryptomator, not to the JVM:

Received launch args: -Djdk.gtk.version=2

In order to be effective, it must be added to the cfg file as described in your link.