Arch Linux Vault Lock fails + fatal Java error

Kryptofreiheit · December 15, 2022, 10:05am

Hallo,

seit gestern bekomme ich aus unerklärlichen Gründen eine Fehlermeldung beim Schließen des Tresors. Eine Datei sei geöffnet oder ein Prozess greife auf den Tresor zu.

10:44:05.766 [App Background Thread 007] INFO  o.cryptomator.ui.lock.LockWorkflow - Locking Vault failed (forced: false).
org.cryptomator.common.vaults.LockNotCompletedException: Locking of vault Vault still in progress.
	at org.cryptomator.desktop@1.6.16/org.cryptomator.common.vaults.Vault.lock(Vault.java:184)
	at org.cryptomator.desktop@1.6.16/org.cryptomator.ui.lock.LockWorkflow.lock(LockWorkflow.java:63)
	at org.cryptomator.desktop@1.6.16/org.cryptomator.ui.lock.LockWorkflow.call(LockWorkflow.java:57)
	at org.cryptomator.desktop@1.6.16/org.cryptomator.ui.lock.LockWorkflow.call(LockWorkflow.java:34)
	at javafx.graphics@19-internal/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

Der Fehler scheint bekannt zu sein, eine richtige Lösung habe ich im Forum aber nicht gefunden.

Darüber hinaus habe ich entdeckt, das seit Monaten Java Fehlerlogs erstellt. Hier nur ein Auszug des recht langen Logs.


# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f832aa3bf0c, pid=2055, tid=3151
#
# JRE version: OpenJDK Runtime Environment (19.0.1+10) (build 19.0.1+10)
# Java VM: OpenJDK 64-Bit Server VM (19.0.1+10, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  [libc.so.6+0x3af0c]
#
# 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" (or dumping to /home/alex/core.2055)
#
# If you would like to submit a bug report, please visit:
#   https://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.
#

---------------  S U M M A R Y ------------

Command Line: -Djpackage.app-version=1.6.16 -Xss5m -Xmx256m -Dfile.encoding=utf-8 -Dcryptomator.logDir=~/.local/share/Cryptomator/logs -Dcryptomator.pluginDir=~/.local/share/Cryptomator/plugins -Dcryptomator.settingsPath=~/.config/Cryptomator/settings.json:~/.Cryptomator/settings.json -Dcryptomator.p12Path=~/.config/Cryptomator/key.p12 -Dcryptomator.ipcSocketPath=~/.config/Cryptomator/ipc.socket -Dcryptomator.mountPointsDir=~/.local/share/Cryptomator/mnt -Dcryptomator.showTrayIcon=false -Dcryptomator.buildNumber=aur-1 -Dcryptomator.appVersion=1.6.16 --module-path=/opt/cryptomator/lib/app/mods -Djpackage.app-path=/opt/cryptomator/bin/cryptomator -Djdk.module.main=org.cryptomator.desktop org.cryptomator.desktop/org.cryptomator.launcher.Cryptomator

Host: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz, 8 cores, 7G, Arch Linux
Time: Wed Dec 14 10:31:21 2022 CET elapsed time: 1459.968567 seconds (0d 0h 24m 19s)

Hat jemand Tipps oder müssen die Entwickler ran?

SailReal · December 15, 2022, 8:48pm

Hey und willkommen in der Cryptomator Community ,

wie hast du Cryptomator installiert? AUR (cryptomator oder cryptomator-bin), Flatpak, oder AppImage?

Kryptofreiheit · December 15, 2022, 9:36pm

Hey,

ich habe über AUR cryptomator installiert.

SailReal · December 16, 2022, 10:24am

Does it also happen when you run the AppImage?

Kryptofreiheit · December 16, 2022, 12:07pm

Yes, locking the vault still fails when using the AppImage. To make matters worse, files in the vault won’t open at all, but this should be none of your concerns as the AUR version works fine in this regard.

Blöd.

Kryptofreiheit · December 20, 2022, 3:49pm

I think I found a solution for the locking issue.

So, Cryptomator opens a new Dolphin window when you click on the “reveal drive” button after unlocking the vault. If you have already opened Dolphin, Cryptomator opens a second window/instance.
It appears that you have to close the entire newly opened (second) Dolphin window in order to lock the vault. Closing any file from the vault won’t suffice.
I am not sure if this is a bug or not, but it feels like one. Hope that helps someone.

SailReal · December 20, 2022, 4:44pm

That sounds interesting. Can you please try the following:

Start Cryptomator
Unlock the vault
Reveal the vault folder
Execute lsof PATH_TO_YOUR_MOUNTED_VAULT_FOLDER e.g.
lsof /home/julian/vault_3000_mounted
from outside of the vault folder.

Is a process in the result list?

Kryptofreiheit · December 20, 2022, 8:01pm

There seem to be 4 processes:

COMMAND     PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
dolphin   58994 alex  cwd    DIR   0,65    12288    1 /home/alex/.local/share/Cryptomator/mnt/Vault
kioslave5 59013 alex  cwd    DIR   0,65    12288    1 /home/alex/.local/share/Cryptomator/mnt/Vault
kioslave5 59015 alex  cwd    DIR   0,65    12288    1 /home/alex/.local/share/Cryptomator/mnt/Vault
kioslave5 60972 alex  cwd    DIR   0,65    12288    1 /home/alex/.local/share/Cryptomator/mnt/Vault