cryptomator
Cryptomator Flatpak unlock UI loop
Please agree to the following
- [X] I have searched existing issues for duplicates
- [X] I agree to follow this project's Code of Conduct
Summary
Cryptomator goes into an endless loop when trying to unlock
What software is involved?
- Operating System: Gentoo unstable , OpenSUSE TW
- Cryptomator: 1.14.2
Volume Type
FUSE
Steps to Reproduce
- Install the latest Cryptomator Flatpak on one of the above mentioned Operating-systems.
- Enter the correct key for the vault
Expected Behavior
Cryptomator should unlock and show me the "Reveal drive" message
Actual Behavior
Cryptomator enters the unlock animation and the drive is mounted at the specified location. Cryptomator is unusable though and will remain in the unlock animation indefinetly.
Reproducibility
Always
Relevant Log Output
F: Not sharing "/etc/ld.so.conf.d" with sandbox: Path "/etc" is reserved by Flatpak
23:18:48.051 [main] INFO o.c.common.settings.SettingsProvider - Settings loaded from /home/flo/.config/Cryptomator/settings.json
23:18:48.087 [main] INFO org.cryptomator.common.Environment - user.home: /home/flo
23:18:48.087 [main] INFO org.cryptomator.common.Environment - java.library.path: :/app/Cryptomator/lib/app:/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
23:18:48.087 [main] INFO org.cryptomator.common.Environment - user.language: en
23:18:48.087 [main] INFO org.cryptomator.common.Environment - user.region: null
23:18:48.087 [main] INFO org.cryptomator.common.Environment - logback.configurationFile: null
23:18:48.087 [main] INFO org.cryptomator.common.Environment - cryptomator.settingsPath: /home/flo/.config/Cryptomator/settings.json:~/.Cryptomator/settings.json
23:18:48.087 [main] INFO org.cryptomator.common.Environment - cryptomator.ipcSocketPath: /home/flo/.config/Cryptomator/ipc.socket
23:18:48.087 [main] INFO org.cryptomator.common.Environment - cryptomator.integrationsWin.keychainPaths: null
23:18:48.087 [main] INFO org.cryptomator.common.Environment - cryptomator.p12Path: /home/flo/.config/Cryptomator/key.p12
23:18:48.087 [main] INFO org.cryptomator.common.Environment - cryptomator.logDir: null
23:18:48.087 [main] INFO org.cryptomator.common.Environment - cryptomator.loopbackAlias: null
23:18:48.088 [main] INFO org.cryptomator.common.Environment - cryptomator.mountPointsDir: /home/flo/.local/share/Cryptomator/mnt
23:18:48.088 [main] INFO org.cryptomator.common.Environment - cryptomator.minPwLength: null
23:18:48.088 [main] INFO org.cryptomator.common.Environment - cryptomator.appVersion: 1.14.2
23:18:48.088 [main] INFO org.cryptomator.common.Environment - cryptomator.buildNumber: flatpak-1
23:18:48.088 [main] INFO org.cryptomator.common.Environment - cryptomator.pluginDir: /home/flo/.local/share/Cryptomator/plugins
23:18:48.088 [main] INFO org.cryptomator.common.Environment - cryptomator.showTrayIcon: true
23:18:48.088 [main] INFO org.cryptomator.common.Environment - cryptomator.disableUpdateCheck: true
23:18:48.088 [main] INFO o.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.14.2 on Linux 6.12.1-gentoo-custom-kernel (amd64)
23:18:48.096 [main] INFO org.cryptomator.ipc.Server - Spawning IPC server listening on socket /home/flo/.config/Cryptomator/ipc.socket
(cryptomator:2): GLib-GIO-WARNING **: 23:18:48.385: Can't find module 'dconf' specified in GSETTINGS_BACKEND
23:18:48.545 [JavaFX Application Thread] INFO o.cryptomator.launcher.Cryptomator - JavaFX runtime started after 670ms
23:18:48.642 [JavaFX Application Thread] ERROR o.purejava.appindicator.AppIndicator - Directory '/etc/ld.so.conf.d/' does not exist
23:18:48.643 [JavaFX Application Thread] INFO o.purejava.appindicator.AppIndicator - Native code library libayatana-appindicator3.so.1 failed to load
23:18:48.643 [JavaFX Application Thread] INFO o.purejava.appindicator.AppIndicator - Native code library libappindicator3 successfully loaded
23:18:48.932 [JavaFX Application Thread] INFO o.f.d.c.transports.TransportBuilder - Using transport dbus-java-transport-native-unixsocket for address unix:path=/run/flatpak/bus
23:18:48.957 [JavaFX Application Thread] INFO o.f.d.c.transports.TransportBuilder - Using transport dbus-java-transport-native-unixsocket for address unix:path=/run/flatpak/bus
23:18:48.961 [JavaFX Application Thread] INFO o.f.d.c.transports.TransportBuilder - Using transport dbus-java-transport-native-unixsocket for address unix:path=/run/flatpak/bus
Anything else?
I tried:
Playing around with the flatpak permissions and reset them to default. Deleting the Cryptomator Flatpak and config files in my home dir. Debugging with strace. Running the Appimage directly (This actually worked) Checking the vaults integrity (all checks passed)
Hi,
I downloaded OpenSUSE TW, installed it and, on an otherwise unchanged system, installed org.cryptomator.Cryptomator from Flathub. Flatpak was already installed.
Cryptomator runs without any issues. I did not change the Cryptomator settings, so the default volume type is set to Automatic and so used FUSE. These are the packages installed on my box:
ralph@localhost:~> sudo zypper search fuse | grep ^i
i | fuse | Reference implementation of the "Filesystem in Userspace" | Paket
i | fuse3 | Reference implementation of the "Filesystem in Userspace" | Paket
i | gvfs-fuse | VFS functionality for GLib | Paket
i | libfuse2 | Library of FUSE, the User space File System for GNU/Linux and BSD | Paket
i | libfuse3-3 | Library of FUSE, the User space File System for GNU/Linux and BSD | Paket
HTH
Edit: typo
@FloTheSysadmin Is the issue still present. According to @purejava on a fresh system, there was no problem.
Unfortunatly the issue still persists, this time on gentoo stable
Are you running the current Cryptomator 1.17.1 then?
I do not have a gentoo box available, but gave current Tumbleweed another whirl with the latest Cryptomator 1.17.1 and another DE - KDE this time. Again, I could not reproduce the issue.
Please provide a log of a failing vault opening operation.