Running the latest Cryptomator 1.7.1 here. After my vault auto-locks from inactivity (verified by going to Finder and check the root system folder – the Cryptomator volume had disappeared), the main Cryptomator app interface is still showing the vault as mounted, with the “lock” button on screen as well allowing me to lock the vault manually (although the “reveal drive” button has gone).
infeo
March 7, 2023, 9:59am
#2
Thank you reporting this! There exists already a ticket for it on our issue tracker and the issue will be fixed with the next patch release:
opened 01:33AM - 04 Mar 23 UTC
type:bug
state:confirmed
misc:gui
### Please agree to the following
- [X] I have searched [existing issues](https… ://github.com/cryptomator/cryptomator/issues?q=) for duplicates
- [X] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md)
### Summary
Vault does not indicate it is locked after idle time has elapsed
### What software is involved?
- Operating System: Linux Mint Debian Edition 5
- Cryptomator: cryptomator-1.7.0-x86_64.AppImage and cryptomator-1.7.1-x86_64.AppImage
- …I have clicked the "Lock when idle for" 15 "minutes"
- On previous versions, including 1.6.4, the Vault would lock, and when I would check my list of Vaults on the left side in Cryptomator, it would show a locked padlock. With the two most recent versions, after idle time has elapsed, the Vault shows as unlocked, although it is, in fact, locked.
### Volume Type
None
### Steps to Reproduce
1. [First Step] Launch Cryptomator 1.7.0 or 1.7.1
2. [Second Step] Use Vault Options to set "Lock when idle for ____ minutes" and set for 15 minutes. When the period has passed, make Cryptomator the focused app, and looking at list of Vaults on the left, notice the Vault set to lock after the specified time, does NOT suggest it is locked. (open padlock)
3. …Try to access the Vault contents, but it will be locked. Return to Cryptomator, lock the Vault, it shows it is locked. Then unlock the Vault, and will in fact be uklocked again.
### Expected Behavior
When the idle time has passed, I expect to see the green padlock "locked", and the Vault to actually be locked.
### Actual Behavior
When the idle time has passed, the green padlock is not "locked", though the Vault is locked.
### Reproducibility
Always
### Relevant Log Output
_No response_
### Anything else?
I love Cryptomator, and have used it on several platforms for years. I have contributed to the project several times, and greatly appreciate all the work you have done to create an incomparable application. I realize this is not a big issue, but thought it was worthy of your attention. Thank you, Stan.
Ahh sorry about that. Didn’t realize there is an existing ticket already. Glad to hear it’ll be fixed in the next patch though!