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

Question

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

matthieugras opened this issue 6 years ago · comments

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 · Answer 1 · Sun Nov 04 2018 21:57:49 GMT+0800 (China Standard Time)

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

xelra · Answer 2 · Wed Dec 12 2018 08:01:02 GMT+0800 (China Standard Time)

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 · Answer 3 · Wed Dec 12 2018 15:40:37 GMT+0800 (China Standard Time)

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

Felix Lechner · Answer 4 · Wed Dec 12 2018 19:41:50 GMT+0800 (China Standard Time)

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.

Felix Lechner · Answer 5 · Wed Dec 12 2018 19:50:22 GMT+0800 (China Standard Time)

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 · Answer 6 · Thu Dec 13 2018 03:46:11 GMT+0800 (China Standard Time)

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

rfjakob · Answer 7 · Thu Dec 13 2018 04:36:07 GMT+0800 (China Standard Time)

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 · Answer 8 · Thu Dec 13 2018 04:45:22 GMT+0800 (China Standard Time)

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

matthieugras · Answer 9 · Thu Dec 13 2018 19:10:29 GMT+0800 (China Standard Time)

On Wednesday, December 12, 2018 9:45:23 PM CET rfjakob wrote: @xelra @matthieugras does gocryptfs v1.6.1 fix the issue?

I'm sorry, I can't test it because I'm not using Fedora anymore

xelra · Answer 10 · Fri Dec 14 2018 01:58:34 GMT+0800 (China Standard Time)

@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 · Answer 11 · Sun Dec 16 2018 00:28:01 GMT+0800 (China Standard Time)

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

Thanks for testing!