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 · 11 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.

Answer 1 · 2018-11-04T13:57:49.000Z

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

Answer 2 · 2018-12-12T00:01:02.000Z

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.

Answer 3 · 2018-12-12T07:40:37.000Z

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

Answer 4 · 2018-12-12T11:41:50.000Z

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.

Answer 5 · 2018-12-12T11:50:22.000Z

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

Answer 6 · 2018-12-12T19:46:11.000Z

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

Answer 7 · 2018-12-12T20:36:07.000Z

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.

Answer 8 · 2018-12-12T20:45:22.000Z

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

Answer 9 · 2018-12-13T11:10:29.000Z

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

Answer 10 · 2018-12-13T17:58:34.000Z

@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.

Answer 11 · 2018-12-15T16:28:01.000Z

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

Thanks for testing!