Cyberduck
Mountain Duck
CLIOpened on Jan 4, 2019 at 6:10:52 PM
Last modified on Sep 11, 2019 at 2:10:39 PM
#10566 reopened defect
Vaults are not detected
| Reported by: | MattiSG | Owned by: | dkocher |
|---|---|---|---|
| Priority: | normal | Milestone: | 8.0 |
| Component: | cryptomator | Version: | Nightly Build |
| Severity: | major | Keywords: | cryptomator |
| Cc: | Architecture: | Intel | |
| Platform: | macOS 10.14 |
Description
Steps to reproduce:
- Create a new Cryptomator vault
- Open the newly created vault.
- Vault folder opens and displays encrypted files. No password prompt, even when refreshing.
Similar to #10422, but the “Auto detect and open vault in browser” preference is checked. Similar to #10352, but on the GUI, not the CLI, and the vault is never detected, not randomly.
- - -
I already had this issue in October and waited for a couple releases before trying again.
Attachments (1)
Change History (13)
Changed on Jan 4, 2019 at 6:11:46 PM by MattiSG
comment:1 Changed on Jan 23, 2019 at 1:08:08 PM by dkocher
- Milestone set to 6.9.2
- Owner set to dkocher
- Status changed from new to assigned
- Summary changed from Cryptomator vaults are not detected to Vaults are not detected
comment:2 Changed on Jan 23, 2019 at 1:10:40 PM by dkocher
- Resolution set to worksforme
- Status changed from assigned to closed
I cannot reproduce with version 6.9.0 testing using OpenStack OVH Storage.
comment:3 follow-up: ↓ 4 Changed on Jan 23, 2019 at 2:59:14 PM by MattiSG
- Resolution worksforme deleted
- Status changed from closed to reopened
I just updated to 6.9.0 (29768) and I get the exact same behaviour with an OVH-provided storage (set up to “Swift (OpenStack Object Storage)”). I can give access to the faulty server if that can help.
(I'm not sure of the expected process here so I reopened, sorry if that's not how you prefer to work, please let me know how you expect to deal with such unresolved issues :) )
comment:4 in reply to: ↑ 3 Changed on Jan 23, 2019 at 3:08:42 PM by dkocher
Replying to MattiSG:
I just updated to 6.9.0 (29768) and I get the exact same behaviour with an OVH-provided storage (set up to “Swift (OpenStack Object Storage)”). I can give access to the faulty server if that can help.
(I'm not sure of the expected process here so I reopened, sorry if that's not how you prefer to work, please let me know how you expect to deal with such unresolved issues :) )
Thanks for letting us know – we will continue to look into this and trying to reproduce.
comment:5 Changed on Jan 31, 2019 at 1:23:04 PM by dkocher
- Milestone changed from 6.9.2 to 6.9.3
Ticket retargeted after milestone closed
comment:6 Changed on Feb 15, 2019 at 12:08:10 PM by dkocher
- Milestone changed from 6.9.3 to 7.0
Ticket retargeted after milestone closed
comment:7 Changed on Feb 15, 2019 at 1:47:51 PM by dkocher
#10352 closed as duplicate.
comment:8 Changed on May 31, 2019 at 1:42:59 PM by dkocher
- Milestone changed from 7.0 to 7.1
comment:9 Changed on Jun 4, 2019 at 12:02:18 PM by dkocher
#10723 closed as duplicate.
comment:10 Changed on Sep 2, 2019 at 7:37:11 PM by dkocher
- Resolution set to worksforme
- Status changed from reopened to closed
comment:11 Changed on Sep 8, 2019 at 4:58:44 PM by MattiSG
- Resolution worksforme deleted
- Status changed from closed to reopened
- Version changed from 6.8.3 to Nightly Build
Tested with version 7.1.0 (31365), still the same :(
comment:12 Changed on Sep 11, 2019 at 2:10:39 PM by dkocher
- Milestone changed from 7.1 to 8.0
Ticket retargeted after milestone closed
Screencast of the issue