Cryptomator Application Crash when using FUSE

English Applications
1

Multiple users, myself included have reported this issue to the app devs of cryptomator ( https://github.com/cryptomator/cryptomator ) but apparently this happens only on OpenSuse Tumbleweed, so they believe there might be an error in OpenSuse Tumbleweed, to quote infeo who answered on my post on github: “special kernel compiling for fuse?”

See also
https://community.cryptomator.org/t/cryptomator-crashes-with-sigsegv-0xb-when-unlocking-vault/5614

My bug report https://github.com/cryptomator/cryptomator/issues/1370

I hope you can help to solve this issue, as it’s the primary reason why I have to constantly switch to another OS.

Regards
Xathros1

2

First,
If you want to report a problem, posting here won’t do anything except non-debugging people will see it. Nothing will be done.
Submit any problems to https://bugzilla.opensuse.org

Next…
IMO the bug isn’t likely with Tumbleweed but possibly something very newly changed that’s found in Tumbleweed, more likely some kind of upstream component. If someone can’t narrow down what and where the problem is, it’s problematic when the problem will be analyzed properly and fixed.

Skimming your bug report and bugzilla reference,
I see logfiles which may mean something to someone but probably requires low level knowledge how the app works which you won’t find anywhere but the app’s own maintenance.
Besides what you’ve done, I recommend you collect relevant system log entries which is more usable for general purpose troubleshooting.
Although you can parse the system log, it’s far easier to collect entries in real time if you can make the problem happen on demand…
Run the following command in a windowed console which will display the system log in real time and leave it open.

journalctl -f

Now, with the above console tucked to the side, invoke your problem preferably from a command command line but can also be by menu entry or other graphical pointer.
Observe what displays in the first console.
Copy the contents and save to assist troubleshooting. You can post to this thread for others to comment, you should include in a bug report, maybe even return to the other references you provided.

TSU

3

Hello, thanks for clarifying where the bug reports should go. I’m certainly not familiar with the matter.

Here’s the error log with the method you described:

Okt 22 13:39:45 linux.fritz.box kded5[3042]: Registering ":1.47/StatusNotifierItem" to system tray
Okt 22 13:39:45 linux.fritz.box xembedsniproxy[3059]: Container window visible, stack below
Okt 22 13:39:46 linux.fritz.box plasmashell[3061]: **file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qm**
l:285:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo
(<arguments>) { ... }
Okt 22 13:39:54 linux.fritz.box plasmashell[3061]: **file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qm**
l:285:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo
(<arguments>) { ... }
Okt 22 13:39:57 linux.fritz.box kded5[3042]: Service  ":1.47" unregistered
Okt 22 13:39:57 linux.fritz.box systemd[2838]: home-cb-.local-share-Cryptomator-mnt-tiLe5cNk3dlw_3.mount: Succeeded. 
Okt 22 13:39:57 linux.fritz.box systemd[2838]: tmp-.mount_cryptohbRbw6.mount: Succeeded.

The application crashes after that line. Every single time.

4

I also created a bugzilla report linked to this thread so that maybe this is getting more attention. https://bugzilla.opensuse.org/show_bug.cgi?id=1178013

5

Hi
So this is a self compiled application? If so have you updated to the latest Tumbleweed snapshot and rebuilt it?

6

There are essentially two versions.
-AppImage
-BuildKit

both suffer from the same crash on Tumbleweed (only).

Yes , even on latest version, snapshot 2020-10-21

Here’s the log from the “build-kit”

cb@localhost:~/Downloads/buildkit-linux> ./launcher-linux.sh  
17:26:33.312 [main] DEBUG org.cryptomator.common.Environment - java.library.path: /usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr
/lib 
17:26:33.315 [main] DEBUG org.cryptomator.common.Environment - user.language: de 
17:26:33.315 [main] DEBUG org.cryptomator.common.Environment - user.region: null 
17:26:33.315 [main] DEBUG org.cryptomator.common.Environment - logback.configurationFile: null 
17:26:33.315 [main] DEBUG org.cryptomator.common.Environment - cryptomator.settingsPath: ~/.config/Cryptomator/settings.json 
17:26:33.315 [main] DEBUG org.cryptomator.common.Environment - cryptomator.ipcPortPath: ~/.config/Cryptomator/ipcPort.bin 
17:26:33.315 [main] DEBUG org.cryptomator.common.Environment - cryptomator.keychainPath: null 
17:26:33.315 [main] DEBUG org.cryptomator.common.Environment - cryptomator.logDir: ~/.local/share/Cryptomator/logs 
17:26:33.315 [main] DEBUG org.cryptomator.common.Environment - cryptomator.mountPointsDir: ~/.local/share/Cryptomator/mnt 
17:26:33.315 [main] DEBUG org.cryptomator.common.Environment - cryptomator.minPwLength: null 
17:26:33.315 [main] DEBUG org.cryptomator.common.Environment - cryptomator.buildNumber: null 
17:26:33.335 [main] DEBUG org.cryptomator.common.ShutdownHook - Registered shutdown hook. 
17:26:33.393 [main] DEBUG org.cryptomator.common.settings.SettingsProvider - Attempting to load settings from /home/cb/.config/Crypt
omator/settings.json 
17:26:33.417 [main] INFO org.cryptomator.common.settings.SettingsProvider - Settings loaded from /home/cb/.config/Cryptomator/settin
gs.json 
17:26:33.670 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.8 on Linux 5.8.15-1-default (amd64) 
17:26:33.966 [JavaFX Application Thread] INFO  o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started. 
17:26:34.151 [JavaFX Application Thread] ERROR o.f.secret.handlers.MessageHandler - org.freedesktop.dbus.exceptions.DBusException: o
rg.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files 
17:26:45.189 [App Background Thread 003] INFO  org.cryptomator.common.vaults.Vault - Storing file name length limit of 220 
# 
# A fatal error has been detected by the Java Runtime Environment: 
# 
#  SIGSEGV (0xb) at pc=0x00007ff8241ee189, pid=3540, tid=3686 
# 
# JRE version: OpenJDK Runtime Environment (15.0+14) (build 15-internal+14-suse-1.9-x8664) 
# Java VM: OpenJDK 64-Bit Server VM (15-internal+14-suse-1.9-x8664, mixed mode, tiered, compressed oops, g1 gc, linux-amd64) 
# Problematic frame: 
# C  [jffi8608120536213508669.so+0x7189] 
# 
# Core dump will be written. Default location: Core dumps may be processed with "/bin/false" (or dumping to /home/cb/Downloads/build
kit-linux/core.3540) 
# 
# An error report file with more information is saved as: 
# /home/cb/Downloads/buildkit-linux/hs_err_pid3540.log 
# 
# If you would like to submit a bug report, please visit: 
#   https://bugreport.java.com/bugreport/crash.jsp 
# 
./launcher-linux.sh: Zeile 11:  3540 Abgebrochen             (Speicherabzug geschrieben) java -cp "libs/*" -Dcryptomator.settingsPat
h="~/.config/Cryptomator/settings.json" -Dcryptomator.ipcPortPath="~/.config/Cryptomator/ipcPort.bin" -Dcryptomator.logDir="~/.local
/share/Cryptomator/logs" -Dcryptomator.mountPointsDir="~/.local/share/Cryptomator/mnt" -Djdk.gtk.version=2 -Xss20m -Xmx512m org.cryp
tomator.launcher.Cryptomator
7

You say the problem happens immediately after the app mounts a filesystem successfully.
The app developers probably would best know what happens immediately afterwards, but it’s probably logical the next step would be to read the contents of the filesystem.
This is also supported by the Java error you’re throwing (so another clue, it’s in the java code) that a SIGSEGV error is thrown which is a memory access violation.
IMO that should be easy for the app developers to track down, this kind of error really shouldn’t happen coding in a managed code language like Java… The app developers have to be doing something like an interop (which is accessing or using code that is alien to the native code) to throw this kind of error, and should stand out like a sore thumb in the entire body of code.

I recommend you show the error to the app developers… This has all the hallmarks of their problem and not an error in TW or anything from upstream by Tumbleweed… There is always a tiny possibility it could be a component provided by Tumbleweed, but is soooo unlikely…
The app developers will also know what Java components they are using which can narrow possibilities, although openjdk is a dependency I don’t know if that is only to hold the JavaFX components from Maven when you build.

TSU

8

it certainly looks like the way you describe it, that the problem is not with openSUSE Tumbleweed.

When you talk about the filesystem, don’t you necessarily mean e.g. the used BTRFS? Could this also cause an error?

9

Not necessarily.
The app developers will know exactly how that part works, and I’m cautioned by all those references to FUSE in your earlier bugzilla reference and even in the title of this thread.
The conversation (which I’m not trying to think deeply about because it’d be the start of digging 'way, 'way deeper) suggests the use of an overlay filesystem

https://wiki.archlinux.org/index.php/Overlay_filesystem

TSU

10

Looks like the developers were wrong when they referred the application crash to special features of openSUSE Tumbleweed, because the problem now also occurs with new Ubuntu version 20.10.

Tried it out (on live usb):
Ubuntu 20.10
64-bit
GNOME 3.38.1

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fbb585ee189, pid=6558, tid=7092
#
# JRE version: OpenJDK Runtime Environment Zulu14.29+23-CA (14.0.2+12) (build 14.0.2+12)
# Java VM: OpenJDK 64-Bit Server VM Zulu14.29+23-CA (14.0.2+12, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  [jffi4261450707072693211.so+0x7189]

systemlog

Oct 23 11:05:58 ubuntu AppRun[7283]: Failed to load module "canberra-gtk-module"
Oct 23 11:05:58 ubuntu org.freedesktop.FileManager1[7283]: 11:05:58.958 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.8 on Linux 5.8.0-25-generic (amd64)
Oct 23 11:05:59 ubuntu org.freedesktop.FileManager1[7283]: 11:05:59.153 [JavaFX Application Thread] INFO  o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
Oct 23 11:05:59 ubuntu org.freedesktop.FileManager1[7283]: 11:05:59.451 [JavaFX Application Thread] ERROR o.f.secret.handlers.MessageHandler - org.freedesktop.dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/secrets/collection/login
Oct 23 11:06:00 ubuntu gnome-shell[5623]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e00004
Oct 23 11:06:00 ubuntu gnome-shell[5623]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e00004
Oct 23 11:06:14 ubuntu systemd[1]: systemd-timedated.service: Succeeded.
Oct 23 11:06:24 ubuntu org.freedesktop.FileManager1[7283]: 11:06:24.911 [App Background Thread 003] INFO  org.cryptomator.common.vaults.Vault - Storing file name length limit of 220
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: #
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: # A fatal error has been detected by the Java Runtime Environment:
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: #
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: #  SIGSEGV (0xb) at pc=0x00007f65fc3ed189, pid=7283, tid=7423
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: #
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: # JRE version: OpenJDK Runtime Environment Zulu14.29+23-CA (14.0.2+12) (build 14.0.2+12)
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: # Java VM: OpenJDK 64-Bit Server VM Zulu14.29+23-CA (14.0.2+12, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: # Problematic frame:
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: # C  [jffi17449612571713990617.so+0x7189]
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: #
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /home/ubuntu/Downloads/core.7283)
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: #
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: # An error report file with more information is saved as:
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: # /home/ubuntu/Downloads/hs_err_pid7283.log
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: #
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: # If you would like to submit a bug report, please visit:
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: #   http://www.azulsystems.com/support/
Oct 23 11:06:25 ubuntu org.freedesktop.FileManager1[7283]: #
Oct 23 11:06:25 ubuntu systemd[2502]: home-ubuntu-.local-share-Cryptomator-mnt-F9EjrZHwK9kF_1.mount: Succeeded.
Oct 23 11:06:25 ubuntu systemd[1]: home-ubuntu-.local-share-Cryptomator-mnt-F9EjrZHwK9kF_1.mount: Succeeded.
Oct 23 11:06:25 ubuntu systemd[2502]: tmp-.mount_cryptoOnSZIV.mount: Succeeded.
Oct 23 11:06:25 ubuntu systemd[1]: tmp-.mount_cryptoOnSZIV.mount: Succeeded.
11

For the time being they released a workaround version @github
>> cryptomator-1.5.8-libffi8-x86_64.AppImage

Maybe this helps someone with the same issue.