Cant auto-unlock vault after login/boot

[HitchRait]

Please agree to the following

• I have searched existing issues for duplicates
• I agree to follow this project's Code of Conduct

Summary

Right after boot Cryptomator shows windows asking to enter vault password, though it should unlock it automatically. I press Cancel, then open menu in system tray, find vault, click Unlock and Cryptomator unlocks it without any prompt. Seems like Cryptomator starts too early and needs some extra time to properly auto-unlock vault.

What software is involved?

• Operating System: Linux 6.1.29-1-MANJARO (amd64) KDE
• Cryptomator: 1.8.0 (Flatpak version)

Volume Type

None

Steps to Reproduce

1. Lock all vaults
2. Logout
3. Login and see a prompt asking for vault password

or

1. Reboot
2. Login and see a prompt asking for vault password

Expected Behavior

1. Lock all vaults
2. Logout
3. Login and vault mounts without any prompt

or

1. Reboot
2. Login and vault mounts without any prompt

Actual Behavior

1. Lock all vaults
2. Logout
3. Login and see a prompt asking for vault password

or

1. Reboot
2. Login and see a prompt asking for vault password

Reproducibility

Always

Relevant Log Output

22:48:26.029 [main] INFO  o.c.common.settings.SettingsProvider - Settings loaded from /home/***/.config/Cryptomator/settings.json
22:48:26.063 [main] INFO  org.cryptomator.common.Environment - user.home: /home/***
22:48:26.063 [main] INFO  org.cryptomator.common.Environment - java.library.path: :/app/Cryptomator/lib/app:/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
22:48:26.063 [main] INFO  org.cryptomator.common.Environment - user.language: en
22:48:26.063 [main] INFO  org.cryptomator.common.Environment - user.region: null
22:48:26.063 [main] INFO  org.cryptomator.common.Environment - logback.configurationFile: null
22:48:26.063 [main] INFO  org.cryptomator.common.Environment - cryptomator.settingsPath: ~/.config/Cryptomator/settings.json:~/.Cryptomator/settings.json
22:48:26.063 [main] INFO  org.cryptomator.common.Environment - cryptomator.ipcSocketPath: ~/.config/Cryptomator/ipc.socket
22:48:26.063 [main] INFO  org.cryptomator.common.Environment - cryptomator.integrationsWin.keychainPaths: null
22:48:26.063 [main] INFO  org.cryptomator.common.Environment - cryptomator.logDir: ~/.local/share/Cryptomator/logs
22:48:26.064 [main] INFO  org.cryptomator.common.Environment - cryptomator.loopbackAlias: null
22:48:26.064 [main] INFO  org.cryptomator.common.Environment - cryptomator.pluginDir: ~/.local/share/Cryptomator/plugins
22:48:26.064 [main] INFO  org.cryptomator.common.Environment - cryptomator.mountPointsDir: ~/.local/share/Cryptomator/mnt
22:48:26.064 [main] INFO  org.cryptomator.common.Environment - cryptomator.minPwLength: null
22:48:26.064 [main] INFO  org.cryptomator.common.Environment - cryptomator.appVersion: 1.8.0
22:48:26.064 [main] INFO  org.cryptomator.common.Environment - cryptomator.buildNumber: flatpak-1
22:48:26.064 [main] INFO  org.cryptomator.common.Environment - cryptomator.showTrayIcon: false
22:48:26.064 [main] INFO  org.cryptomator.common.Environment - cryptomator.p12Path: ~/.config/Cryptomator/key.p12
22:48:26.064 [main] INFO  o.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.8.0 on Linux 6.1.29-1-MANJARO (amd64)
22:48:26.064 [main] DEBUG org.cryptomator.logging.DebugMode - Debug mode enabled
22:48:26.065 [main] DEBUG o.c.launcher.SupportedLanguages - Using system locale
22:48:26.191 [main] INFO  org.cryptomator.ipc.Server - Spawning IPC server listening on socket /home/***/.config/Cryptomator/ipc.socket
22:48:26.426 [main] DEBUG o.c.launcher.IpcMessageHandler - Received launch args: 
22:48:26.429 [main] DEBUG o.cryptomator.launcher.Cryptomator - Did not find running application instance. Launching GUI...
22:48:26.708 [JavaFX Application Thread] INFO  o.cryptomator.launcher.Cryptomator - JavaFX runtime started after 1061ms
22:48:26.713 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
22:48:26.876 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
22:48:26.878 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Found implementation: org.cryptomator.frontend.fuse.mount.LinuxFuseMountProvider in jar /app/Cryptomator/lib/app/mods/fuse-nio-adapter-2.0.5.jar
22:48:26.884 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Found implementation: org.cryptomator.frontend.fuse.mount.MacFuseMountProvider in jar /app/Cryptomator/lib/app/mods/fuse-nio-adapter-2.0.5.jar
22:48:26.885 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Found implementation: org.cryptomator.frontend.fuse.mount.FuseTMountProvider in jar /app/Cryptomator/lib/app/mods/fuse-nio-adapter-2.0.5.jar
22:48:26.886 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Found implementation: org.cryptomator.frontend.fuse.mount.WinFspMountProvider in jar /app/Cryptomator/lib/app/mods/fuse-nio-adapter-2.0.5.jar
22:48:26.886 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Found implementation: org.cryptomator.frontend.fuse.mount.WinFspNetworkMountProvider in jar /app/Cryptomator/lib/app/mods/fuse-nio-adapter-2.0.5.jar
22:48:26.887 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Found implementation: org.cryptomator.frontend.webdav.mount.MacAppleScriptMounter in jar /app/Cryptomator/lib/app/mods/webdav-nio-adapter-2.0.2.jar
22:48:26.887 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Found implementation: org.cryptomator.frontend.webdav.mount.FallbackMounter in jar /app/Cryptomator/lib/app/mods/webdav-nio-adapter-2.0.2.jar
22:48:26.888 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Found implementation: org.cryptomator.frontend.webdav.mount.WindowsMounter in jar /app/Cryptomator/lib/app/mods/webdav-nio-adapter-2.0.2.jar
22:48:26.888 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Found implementation: org.cryptomator.frontend.webdav.mount.LinuxGioMounter in jar /app/Cryptomator/lib/app/mods/webdav-nio-adapter-2.0.2.jar
22:48:26.889 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Found implementation: org.cryptomator.frontend.dokany.mount.DokanyMountProvider in jar /app/Cryptomator/lib/app/mods/dokany-nio-adapter-2.0.0.jar
22:48:26.891 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Implementation is available: org.cryptomator.frontend.fuse.mount.LinuxFuseMountProvider
22:48:26.892 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Implementation is available: org.cryptomator.frontend.webdav.mount.LinuxGioMounter
22:48:26.892 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - MountService: Implementation is available: org.cryptomator.frontend.webdav.mount.FallbackMounter
22:48:26.897 [JavaFX Application Thread] DEBUG o.cryptomator.common.CommonsModule - Starting App Scheduled Executor 01
22:48:26.898 [App Scheduled Executor 01] DEBUG o.cryptomator.common.CommonsModule - Starting App Scheduled Executor 02
22:48:26.900 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
22:48:26.966 [JavaFX Application Thread] TRACE o.cryptomator.ui.fxapp.FxApplication - FxApplication.start()
22:48:27.064 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
22:48:27.066 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - TrayMenuController: Found implementation: org.cryptomator.ui.traymenu.AwtTrayMenuController in jar /app/Cryptomator/lib/app/mods/cryptomator-1.8.0.jar
22:48:27.074 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - TrayMenuController: Implementation is available: org.cryptomator.ui.traymenu.AwtTrayMenuController
22:48:27.122 [JavaFX Application Thread] DEBUG o.c.u.traymenu.AwtTrayMenuController - initialized tray icon
22:48:27.131 [JavaFX Application Thread] DEBUG o.cryptomator.common.CommonsModule - Starting App Background Thread 001
22:48:27.570 [JavaFX Application Thread] DEBUG o.cryptomator.ui.common.FontLoader - Loaded family: Font Awesome 5 Free Solid
22:48:27.594 [JavaFX Application Thread] TRACE o.c.u.m.MainWindowTitleController - init MainWindowTitleController
22:48:27.613 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
22:48:27.614 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - KeychainAccessProvider: Found implementation: org.cryptomator.linux.keychain.KDEWalletKeychainAccess in jar /app/Cryptomator/lib/app/mods/integrations-linux-1.2.0.jar
22:48:27.615 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - KeychainAccessProvider: Found implementation: org.cryptomator.linux.keychain.SecretServiceKeychainAccess in jar /app/Cryptomator/lib/app/mods/integrations-linux-1.2.0.jar
22:48:27.637 [JavaFX Application Thread] INFO  o.f.d.c.transports.TransportBuilder - Using transport dbus-java-transport-native-unixsocket to connect to unix:path=/run/flatpak/bus
22:48:27.685 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - KeychainAccessProvider: Implementation is available: org.cryptomator.linux.keychain.KDEWalletKeychainAccess
22:48:27.687 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - KeychainAccessProvider: Implementation is available: org.cryptomator.linux.keychain.SecretServiceKeychainAccess
22:48:27.689 [JavaFX Application Thread] INFO  o.f.d.c.transports.TransportBuilder - Using transport dbus-java-transport-native-unixsocket to connect to unix:path=/run/flatpak/bus
22:48:27.812 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
22:48:27.813 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - RevealPathService: Found implementation: org.cryptomator.linux.revealpath.DBusSendRevealPathService in jar /app/Cryptomator/lib/app/mods/integrations-linux-1.2.0.jar
22:48:27.814 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - RevealPathService: Implementation is available: org.cryptomator.linux.revealpath.DBusSendRevealPathService
22:48:28.104 [JavaFX Application Thread] TRACE o.c.ui.mainwindow.ResizeController - init ResizeController
22:48:28.110 [JavaFX Application Thread] TRACE o.c.u.m.MainWindowController - init MainWindowController
22:48:28.425 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Main window initialized after 2778ms
22:48:28.439 [JavaFX Application Thread] DEBUG o.c.common.vaults.VaultStats - stop recording stats
22:48:28.441 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - Start unlock workflow for vault-name
22:48:28.448 [JavaFX Application Thread] DEBUG o.cryptomator.common.CommonsModule - Starting App Background Thread 002
22:48:29.308 [DBus-Signal-Receiver-1] INFO  o.f.dbus.handlers.SignalHandler - Received signal KWallet.walletOpened: kdewallet
22:48:29.310 [DBus-Signal-Receiver-1] INFO  o.f.dbus.handlers.SignalHandler - Received signal KWallet.walletAsyncOpened: {TransactionID: 0, handle: 82954917}
22:48:29.311 [DBus-Signal-Receiver-1] INFO  o.f.dbus.handlers.SignalHandler - Received signal KWallet.walletAsyncOpened: {TransactionID: 1, handle: 82954917}
22:48:29.311 [DBus-Signal-Receiver-1] INFO  o.f.dbus.handlers.SignalHandler - Received signal KWallet.walletAsyncOpened: {TransactionID: 2, handle: 82954917}
22:48:29.311 [DBus-Signal-Receiver-1] INFO  o.f.dbus.handlers.SignalHandler - Received signal KWallet.walletAsyncOpened: {TransactionID: 3, handle: 82954917}
22:48:32.596 [JavaFX Application Thread] DEBUG o.cryptomator.common.CommonsModule - Starting App Background Thread 003
22:48:32.597 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.UpdateChecker - Checking for updates...
22:48:33.204 [JavaFX Application Thread] INFO  o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.8.0, lastest version: 1.8.0
22:48:33.549 [JavaFX Application Thread] DEBUG o.c.u.k.m.PassphraseEntryController - Unlock canceled by user.
22:48:33.550 [JavaFX Application Thread] DEBUG o.c.ui.unlock.UnlockWorkflow - Unlock of 'vault-name' canceled.
22:48:33.550 [JavaFX Application Thread] DEBUG o.c.common.vaults.VaultStats - stop recording stats
22:48:35.253 [DBus-Signal-Receiver-1] INFO  o.f.dbus.handlers.SignalHandler - Received signal KWallet.walletAsyncOpened: {TransactionID: 4, handle: 82954917}
22:48:35.254 [DBus-Signal-Receiver-1] INFO  o.f.dbus.handlers.SignalHandler - Received signal KWallet.folderUpdated: {wallet: kdewallet, folder: Nextcloud}
22:48:38.497 [JavaFX Application Thread] DEBUG o.c.common.vaults.VaultStats - stop recording stats
22:48:38.498 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - Start unlock workflow for vault-name
22:48:38.500 [DBus-Signal-Receiver-1] INFO  o.f.dbus.handlers.SignalHandler - Received signal KWallet.walletAsyncOpened: {TransactionID: 5, handle: 82954917}
22:48:38.500 [JavaFX Application Thread] DEBUG o.c.l.k.KDEWalletKeychainAccess - loadPassphrase: wallet is open.
22:48:38.500 [JavaFX Application Thread] DEBUG o.cryptomator.common.CommonsModule - Starting App Background Thread 004
22:48:38.772 [App Background Thread 004] DEBUG o.c.cryptofs.common.BackupHelper - Verified backup file: /home/***/address-to-vault/vault-name/masterkey.cryptomator.FC1CE0CB.bkup
22:48:38.774 [App Background Thread 004] DEBUG o.c.cryptofs.common.BackupHelper - Verified backup file: /home/***/address-to-vault/vault-name/vault.cryptomator.177A84AE.bkup
22:48:38.785 [App Background Thread 004] DEBUG o.cryptomator.cryptofs.ReadonlyFlag - Vault opened for read and write.
22:48:38.977 [Thread-16] TRACE o.c.frontend.fuse.ReadOnlyAdapter - getattr /jfuse_mount_probe failed, node not found
22:48:38.980 [App Background Thread 004] DEBUG o.c.l.k.KDEWalletKeychainAccess - Passphrase was not stored.
22:48:38.981 [JavaFX Application Thread] INFO  o.c.ui.unlock.UnlockWorkflow - Unlock of 'vault-name' succeeded.
22:48:38.984 [JavaFX Application Thread] DEBUG o.c.common.vaults.VaultStats - start recording stats
22:48:38.987 [JavaFX Application Thread] DEBUG o.cryptomator.common.CommonsModule - Starting App Background Thread 005
22:48:39.986 [JavaFX Application Thread] DEBUG o.cryptomator.common.CommonsModule - Starting App Background Thread 006
22:48:42.814 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
22:48:43.830 [App Scheduled Executor 01] DEBUG o.c.common.settings.SettingsProvider - Attempting to save settings to /home/***/.config/Cryptomator/settings.json
22:48:43.834 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to /home/***/.config/Cryptomator/settings.json
22:48:44.706 [Thread-15] TRACE o.c.frontend.fuse.ReadOnlyAdapter - getattr / (lastModifiedTime: 2023-04-19T16:23:47.002161144Z, lastAccessTime: 2023-01-24T17:26:12Z, creationTime: 2023-04-19T16:23:47.002161144Z, isRegularFile: false, isDirectory: true, isSymbolicLink: false, isOther: false, size: 4096, fileKey: (dev=fe00,ino=531972))
22:48:44.838 [Thread-15] TRACE o.c.frontend.fuse.ReadOnlyAdapter - getattr /.directory (lastModifiedTime: 2023-03-12T14:38:07.867842939Z, lastAccessTime: 2023-05-22T19:47:30.365432703Z, creationTime: 2023-03-12T14:38:07.867842939Z, isRegularFile: true, isDirectory: false, isSymbolicLink: false, isOther: false, size: 93, fileKey: (dev=fe00,ino=536017))
22:48:44.841 [Thread-15] TRACE o.c.frontend.fuse.ReadOnlyAdapter - open /.directory (0)
22:48:44.845 [Thread-15] TRACE o.c.cryptofs.fh.FileHeaderHolder - Reading file header from /home/***/address-to-vault/vault-name/deleted-seems-sensitive
22:48:44.846 [Thread-15] TRACE o.c.cryptofs.fh.OpenCryptoFile - First channel for this openFile. Initializing file size...
22:48:44.847 [Thread-15] TRACE o.c.frontend.fuse.OpenFileFactory - Opening 1 OpenFile{path=/.directory, channel=org.cryptomator.cryptofs.ch.CleartextFileChannel@5c71cc1e}
22:48:44.848 [Thread-16] TRACE o.c.frontend.fuse.ReadOnlyAdapter - read 4096 bytes from file /.directory starting at 0...
22:48:44.849 [Thread-16] TRACE o.cryptomator.frontend.fuse.OpenFile - Reached EOF
22:48:44.849 [Thread-16] TRACE o.c.frontend.fuse.ReadOnlyAdapter - read 93 bytes from file /.directory
22:48:44.849 [Thread-16] TRACE o.c.frontend.fuse.ReadOnlyAdapter - release /.directory (1)
22:48:44.849 [Thread-16] TRACE o.c.frontend.fuse.OpenFileFactory - Releasing 1 OpenFile{path=/.directory, channel=org.cryptomator.cryptofs.ch.CleartextFileChannel@5c71cc1e}
22:48:44.916 [Thread-15] TRACE o.c.frontend.fuse.ReadOnlyAdapter - statfs / (113422168064 / 244681363456)
22:48:44.926 [Thread-15] TRACE o.c.frontend.fuse.ReadOnlyAdapter - readdir /
22:48:44.929 [Thread-15] TRACE o.c.c.dir.CryptoDirectoryStream - OPEN 
22:48:44.948 [Thread-15] TRACE o.c.c.dir.CryptoDirectoryStream - CLOSE 
22:48:44.949 [Thread-15] TRACE o.c.frontend.fuse.ReadOnlyAdapter - getattr / (lastModifiedTime: 2023-04-19T16:23:47.002161144Z, lastAccessTime: 2023-01-24T17:26:12Z, creationTime: 2023-04-19T16:23:47.002161144Z, isRegularFile: false, isDirectory: true, isSymbolicLink: false, isOther: false, size: 4096, fileKey: (dev=fe00,ino=531972))
22:48:44.950 [Thread-16] TRACE o.c.frontend.fuse.ReadOnlyAdapter - statfs / (113421762560 / 244681363456)

Anything else?

No response

[HitchRait]

Recently figured that on Manjaro GNOME bug is reproduced only when autologin is enabled. If I switch to manual login, it works fine.

[bcpardo]

Getting the same issue here on CachyOS GNOME.

[purejava]

Duplicate of #1950.

This is due to the keychain backends KDE kwallet and GNOME keyring being locked after a reboot / login. GNOME keyring is unlocked from GNOME though, when you manually log in to your GNOME session and therefore Cryptomator can read your password from the GNOME keyring on auto starting Cryptomator.

[npkasenides]

Duplicate of #1950.

This is due to the keychain backends KDE kwallet and GNOME keyring being locked after a reboot / login. GNOME keyring is unlocked from GNOME though, when you manually log in to your GNOME session and therefore Cryptomator can read your password from the GNOME keyring on auto starting Cryptomator.

This is not true in my case. A Cryptomator vault still requires its password on login, even though my login keyring is passwordless. Interestingly, this applies only to the first vault on the list. (GNOME, 1.15.1 flatpak-1)

[Cral0202]

I have the same issue on Fedora 42. It does not automatically unlock after boot, but if I close down the unlock prompt and simply click "unlock", it automatically unlocks without needing to insert a password. I thought maybe KDE Wallet was slow to start or something, so I set a 1 minute delay for Cryptomator to start after boot. But when it boots up after the delay, the exact same issue occurs.

[dazu89]

Same problem as @Cral0202.

[purejava]

This is not true in my case. A Cryptomator vault still requires its password on login, even though my login keyring is passwordless. Interestingly, this applies only to the first vault on the list. (GNOME, 1.15.1 flatpak-1)

I tested this (with a recent version of the flatpaked Cryptomator) and a passwordless GNOME login keyring. It prompts me for the vault password too after a reboot, but due to a still locked keyring. When I set the password of the GNOME login keyring to the same password as of my user account, the GNOME keyring is still locked after a reboot, so this does not help much.

The reason for showing the password login pop-up is that Cryptomator cannot access the stored password in the still locked GNOME keyring. I veryfied this by locking out of my session and manually locking in and Crytomator starts and unlocks the vault without any prompt. This works for the GNOME login keyring password set to "" and to the user password.

[purejava]

I have the same issue on Fedora 42. It does not automatically unlock after boot, but if I close down the unlock prompt and simply click "unlock", it automatically unlocks without needing to insert a password. I thought maybe KDE Wallet was slow to start or something, so I set a 1 minute delay for Cryptomator to start after boot. But when it boots up after the delay, the exact same issue occurs.

Do you auto-login to your KDE session or not?
After your KDE session comes up, is the KDE walltet locked then or unlocked?