I recently switched over to NixOS, specifically the latest stable branch 26.05 which ships Cryptomator version 1.19.2. I’m also running KDE Plasma 6 with Plasma Login Manager.
My workflow up until now relies on a vault that I automatically unlock as soon as I log into my system. When importing the vault again on this new distribution, I filled in the vault password, I checked the “Remember password” flag (so I don’t have to fill in my password every time I want to unlock my vault) and I checked the “Unlock vault when starting Cryptomator” flag in the vault settings.
Currently, however, I’m running into an issue where whenever I launch Cryptomator (both automatically and manually) for the first time after login, my vault prompts me for my password as if the password wasn’t saved.
If I cancel that pop-up and try to unlock it from my system tray, I get the same pop-up again.
However, if I cancel the pop-up and unlock it from the main UI, the vault does unlock without prompting for my password.
I already checked my KDE Wallet (as that’s what I use to store vault passwords); the password is in fact saved correctly.
This is very unexpected behaviour, as these same settings worked just fine on my Debian machine which I used previously. Can someone help me troubleshoot?
sounds like a race with kwallet. cryptomator starts on login before the wallet is actually unlocked so the first prompt thinks theres no saved password. unlocking from the main window works because by then kwallet is up. debian was probably slower to spawn the app so you never noticed. try delaying autostart a few seconds, or dont auto unlock on start and just unlock from the main ui. also check if nixos is launching it as a systemd user service before plasma-kwallet-pam finishes.
This seems to be an issue with any distro that uses KDE. I have tested the remember password option with autostart on both OpenSuse 16 Leap KDE and Fedora 44 KDE. Each time the computer started, it would ask for the vault password. If I close it out and click unlock from the UI, it unlocked without an issue. I tried playing around with settings and even setting an autostart delay of 60 seconds but it made no difference.
Here is the solution. Well a workaround maybe. I found out if I also set a Chromium browser to autostart (tested on Brave and Vivaldi), then Cryptomator vaults would unlock automatically on startup. No autostart delay is needed for the Chromimum browser or Cryptomator. As long as you have them both setup to autostart, the auto unlock always works. I just set the homepage to a news site so I can can at least see whats going on around the world when the browser comes up. I’m wondering if the developers can fix this issue on KDE distros.