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

"No permissions" when copy/paste into Vault #3207

Closed
2 tasks done
McKorleone opened this issue Nov 15, 2023 · 11 comments
Closed
2 tasks done

"No permissions" when copy/paste into Vault #3207

McKorleone opened this issue Nov 15, 2023 · 11 comments
Assignees
Labels
Milestone

Comments

@McKorleone
Copy link

Please agree to the following

Summary

When you want to copy/paste a file into the Vault you get an error which basically says "File already exists" (0KB file) and "You dont have the permissions to do that" (Copy/Paste)

What software is involved?

  • Operating System: Windows 10 Build 19045
  • Cryptomator: 1.11.0

Volume Type

WinFsp (Local Drive)

Steps to Reproduce

  1. Copy a file from Desktop/Download into the Vault
  2. You should see the pop-up "Override file?"
  3. If you click "Ignore", you will see the pop-up "You dont have the permissions to do that"
  4. If you install 1.10.1 instead of 1.11.0 it works

Expected Behavior

Copy/Paste into a Vault is possible

Actual Behavior

Copy/Paste into a Vault is not possible

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

@McKorleone McKorleone added the type:bug Something isn't working label Nov 15, 2023
@infeo
Copy link
Member

infeo commented Nov 16, 2023

@McKorleone Can you do the following:

  1. Start Cryptomator
  2. Create a vault directly in your user directory (e.g. C:\Users\JaneDoe\myVault)
  3. Unlock this vault
  4. Enable Debug mode in Cryptomator
  5. Trigger the problem
  6. Lock the vault
  7. Quit Cryptomator

and send us the log file (named cryptomator0.log)?

If you cannot reproduce the problem with a clean vault, please execute the aforementiond steps with a vault where the problem occurs.

@infeo infeo added state:awaiting-response We need further input from the issue author os:windows mount:fuse labels Nov 16, 2023
@trudolf-msft
Copy link

trudolf-msft commented Nov 16, 2023

Same issue here
cryptomator1.log

@McKorleone
Copy link
Author

@McKorleone Can you do the following:

  1. Start Cryptomator
  2. Create a vault in your user directory
  3. Unlock this vault
  4. Enable Debug mode in Cryptomator
  5. Trigger the problem
  6. Lock the vault
  7. Quit Cryptomator

and send us the log file (named cryptomator0.log)?

If you cannot reproduce the problem with a clean vault, please execute the aforementiond steps with a vault where the problem occurs.

Sure

cryptomator0.log

@Diego-BR

This comment was marked as duplicate.

@infeo

This comment was marked as resolved.

@Diego-BR
Copy link

@Diego-BR Can you also provide Debug-Log with the above instructions?

We already have an idea, where the problem is located, but want to be sure.

Sorry, I don't have the new version installed anymore. But I can add from the tests that I've done that it happened only with specific files, not all of them.

@infeo
Copy link
Member

infeo commented Nov 21, 2023

We have found the cause and a fix is on its way.

Depends on cryptomator/fuse-nio-adapter#86

@infeo infeo self-assigned this Nov 21, 2023
@norbert0511
Copy link

Same issue. But only with files saved by Firefox browser. The same files saved by Microsoft Edge are working well.
May be this info helps!

@alepulver

This comment was marked as off-topic.

@infeo infeo closed this as completed in 6bb5ed1 Nov 24, 2023
@infeo infeo removed the state:awaiting-response We need further input from the issue author label Nov 24, 2023
@infeo infeo added this to the 1.11.1 milestone Nov 28, 2023
@infeo
Copy link
Member

infeo commented Dec 7, 2023

@MatthiasArnold I deleted your comment because the uploaded log file also contained personal information of another, unlocked vault. Ensure, that during the debug session only one vault is unlocked. Lock after the debug session the test vault and close Cryptomator, which also prevents further unrelated write operations into the log file.

Apart from that, your issue does not seem related from the log file. I suggest to open a new ticket.

@cryptomator cryptomator deleted a comment from MatthiasArnold Dec 7, 2023
@MatthiasArnold
Copy link

hi @infeo thanks, thanks for pointing an the other open vault. will open a new ticket and present a new logfile. cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants