Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unlock same name vault failed on Linux using FUSE #3114

Closed
2 tasks done
SailReal opened this issue Sep 13, 2023 · 1 comment
Closed
2 tasks done

Unlock same name vault failed on Linux using FUSE #3114

SailReal opened this issue Sep 13, 2023 · 1 comment
Labels
mount:fuse os:linux state:has-workaround There is a known workaround for the described problem type:bug Something isn't working

Comments

@SailReal
Copy link
Member

SailReal commented Sep 13, 2023

Please agree to the following

Summary

Unlock same name vault failed

What software is involved?

  • Operating System: Linux
  • Cryptomator: 1.10.0
  • FUSE: 3.16.1

Volume Type

FUSE

Steps to Reproduce

  1. Create two vaults with same name(local folder)
  2. Unlock one vault

Expected Behavior

Unlock two vaults with same name

Actual Behavior

Cannot unlock second vault

Reproducibility

Always

Relevant Log Output

Error Code 6HCL:2GTN:8714
org.cryptomator.integrations.mount.MountFailedException: org.cryptomator.jfuse.api.FuseMountFailedException: fuse_mount failed
	at org.cryptomator.frontend.fuse@3.0.0/org.cryptomator.frontend.fuse.mount.LinuxFuseMountProvider$LinuxFuseMountBuilder.mount(LinuxFuseMountProvider.java:116)
	at org.cryptomator.desktop@1.10.0/org.cryptomator.common.mount.Mounter.mount(Mounter.java:138)
	at org.cryptomator.desktop@1.10.0/org.cryptomator.common.vaults.Vault.unlock(Vault.java:150)
	at org.cryptomator.desktop@1.10.0/org.cryptomator.ui.keyloading.KeyLoadingStrategy.use(KeyLoadingStrategy.java:79)
	at org.cryptomator.desktop@1.10.0/org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:70)
	at org.cryptomator.desktop@1.10.0/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:60)
	at org.cryptomator.desktop@1.10.0/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:31)
	at javafx.graphics@20.0.2/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$UniAccept.tryFire(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$Completion.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.cryptomator.jfuse.api.FuseMountFailedException: fuse_mount failed
	at org.cryptomator.jfuse.linux.amd64@0.5.1/org.cryptomator.jfuse.linux.amd64.FuseImpl.mount(FuseImpl.java:35)
	at org.cryptomator.jfuse.api@0.5.1/org.cryptomator.jfuse.api.Fuse.mount(Fuse.java:127)
	at org.cryptomator.frontend.fuse@3.0.0/org.cryptomator.frontend.fuse.mount.LinuxFuseMountProvider$LinuxFuseMountBuilder.mount(LinuxFuseMountProvider.java:113)
	... 13 more

Anything else?

No response

@SailReal SailReal added type:bug Something isn't working os:linux mount:fuse state:has-workaround There is a known workaround for the described problem labels Sep 13, 2023
@SailReal
Copy link
Member Author

Closing in favor of #3344

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mount:fuse os:linux state:has-workaround There is a known workaround for the described problem type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant