Cryptomator can't start: Desktop API is not supported on the current platform #1230
Comments
|
Funnily enough the line in question didn't change for 9 months. I.e. something else must have changed in your setup. That said, we can easily wrap the line with a |
|
The last version I had was Not sure if you would like to place a guard for this kind of scenario(s). If so, keep this one opened until it's added, otherwise feel free to close it... I can start it via |
|
I'm having the same problem. I'm running Arch/Plasma/X11, no wayland. |
|
it isn't an Arch/Plasma problem because I'm running Debian Buster 10.4 and have the same problem (got adoptopenjdk 14). Appimage 1.5.3 is starting and running without problems (the ones before it too) but 1.5.4 and 1.5.5 give me the mentioned "Cryptomator Failed to launch JVM" error. Hope that it will be fixed with 1.5.6 again @overheadhunter |
|
the new 1.5.6 appimage is just debugging when executed and crashes straight after 3 seconds without any error being displayed when I execute it in the terminal. anyone else? summary: |
|
@Distrotube Beginning with version 1.5.4 we re-added |
|
On my Debian Buster VM Cryptomator works as expected. @Distrotube What is your system setup? Installing an JDK does not change the situation, because Cryptomator ships its own JVM. But since you already installed it, can you try to run the buildkit release? Just unzip it an execute the |
|
WORKING SOLUTION BELOW @infeo I'm running Debian Buster x86 (apparently its a 32bit userland with a 64bit kernel on a x64 Intel Atom CPU) following your advice, I get this output without modifying the SOLUTION: That means your precompiled Appimages won't work on my machine anymore and I have to fall back to the buildkit.linux.zip and modify it like this every time a new version gets released? (Or can I turn the modified buildkit into an appimage so that I'm able to use it again as single executable file?) |
@Distrotube see #1167 (comment) @x80486 , @guschtlswife : Can you confirm this? Then we need to think about a strategy for staying on the tightrope between using the option or not. |
|
Actually I would consider this a JavaFX bug, but its probably faster to solve it ourselves, if we find a way to determine the GTK version before launch. |
Confirmed! Removing jdk.gtk.version=2 from launcher-linux.sh makes it working again. Thanks! |
infeo
added
the
state:awaiting-response
|
It doesn't run for me under Arch Linux — but it's because of the GTK version (this happens almost all the time). It does run well under Ubuntu (VM), so I guess it will work. |
no-response
bot
removed
the
state:awaiting-response
that's exactly what should have been fixed in this beta. 😢 |
|
I rechecked: |
|
I started it on Arch linux as well. It does run and work, but prints Debian specific log messages on start: |
|
This alone should not happen. We created a start script checking for the installed gtk version specific to different distros: On arch, |
|
Running that code snippet from which: no dpkg in (/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl) |
I think this is due to the fact that I use zsh instead of bash. while running this on bash returns nothing as you expect it. |
|
It is kind of ugly to check the stdout instead of the exit value anyway. We should avoid
|
|
Fixed in 1.5.9 |
Description
I just downloaded the latest version (
1.5.5) and it doesn't run. Not sure if this is because a missing library in GNOME3.36.2or something with Cryptomator + Linux in general. Where is the Flatpak version anyway 😎System Setup
Linux uplink 5.4.42-1-lts #1 SMP Wed, 20 May 2020 20:42:53 +0000 x86_64 GNU/Linux)Steps to Reproduce
1.5.5Expected Behavior
Cryptomator should start, as the previous versions.
Actual Behavior
Reproducibility
Always
The text was updated successfully, but these errors were encountered: