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

Fedora KDE: Could not change permissions for "file.jpg" #271

Closed
matthieugras opened this issue Oct 17, 2018 · 11 comments
Closed

Fedora KDE: Could not change permissions for "file.jpg" #271

matthieugras opened this issue Oct 17, 2018 · 11 comments
Labels

Comments

@matthieugras
Copy link

I'm getting this error message when I'm trying to copy some files in Dolphin (GUI file explorer) to the the crypted folder. If I copy too many files this opens so many windows that my system freezes.

@rfjakob
Copy link
Owner

rfjakob commented Nov 4, 2018

Hi! I cannot reproduce this problem here. Do you mount from a network drive or something?

Edit: I run Dolphin 18.04.3, screenshot below

screenshot from 2018-11-04 14-56-50

@xelra
Copy link

xelra commented Dec 12, 2018

I've just run into a similar problem on Arch Linux. The system is unable to set attributes and hence chmod doesn't work.

The issue is already tracked there, but seeing that this issue also exists in Fedora, I believe this could be an upstream issue.

I don't know anything about the Fedora package, but in the Arch package, this issue occurred when the build source changed from cloning the repo with tag 1.6 to getting gocryptfs_v1.6_src-deps.tar.gz.

The former also only depended on go-2, while the latter depends on a hell of a lot Haskell packages.

@rfjakob
Copy link
Owner

rfjakob commented Dec 12, 2018

I agree, sounds like a problem in gocryptfs. Can I download the arch linux gocryptfs binary somewhere?

@lechner
Copy link
Contributor

lechner commented Dec 12, 2018

FWIW, I haven't noticed any problems in Debian. We built from gocryptfs_v1.6_src.tar.gz (no deps).

For identification purposes, I attached your relevant upstream signature gocryptfs_v1.6_src.tar.gz.asc.gz (Github required a zipped upload). You can also find hashes here.

@lechner
Copy link
Contributor

lechner commented Dec 12, 2018

You can find version information for our build dependencies in this i386 build log (although I and most other users are probably on amd64)

@rfjakob
Copy link
Owner

rfjakob commented Dec 12, 2018

I can reproduce the problem with gocryptfs_v1.6_src-deps.tar.gz .

@rfjakob
Copy link
Owner

rfjakob commented Dec 12, 2018

So I think you need this commit: 658cc4a . I have released gocryptfs v1.6.1 that includes this commit: https://github.com/rfjakob/gocryptfs/releases/tag/v1.6.1

This only affects users who are on Go 1.11 or higher. Debian has Go 1.10, so I guess that's the difference.

@rfjakob rfjakob added the bug label Dec 12, 2018
@rfjakob
Copy link
Owner

rfjakob commented Dec 12, 2018

@xelra @matthieugras does gocryptfs v1.6.1 fix the issue?

@matthieugras
Copy link
Author

matthieugras commented Dec 13, 2018 via email

@xelra
Copy link

xelra commented Dec 13, 2018

@rfjakob I can confirm that the issue is fixed with v1.6.1. I was also seeing the EOPNOTSUPP errors, so I think the fix was spot on.

Strange that the error only showed on a certain build source.

IMO this issue can be closed.

@rfjakob
Copy link
Owner

rfjakob commented Dec 15, 2018

My guess is that the move from AUR also changed the Go version that was used to build gocryptfs?

Thanks for testing!

@rfjakob rfjakob closed this as completed Dec 15, 2018
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

4 participants