Bug 369647 - Copy or move operations to encfs folders in a NTFS filesystem show 'could not change permissions for <path/filename>'
Summary: Copy or move operations to encfs folders in a NTFS filesystem show 'could not...
Status: CONFIRMED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.45.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-02 18:40 UTC by João Vidal da Silva
Modified: 2025-03-24 22:58 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description João Vidal da Silva 2016-10-02 18:40:47 UTC 
Copying or moving files to an encfs folder in a NTFS filesystem/partiton will show the message 'could not change permissions for <path/filename>'.
It doesn't happen if the operation is done directly to NTFS.

Reproducible: Always

Steps to Reproduce:
1. Create/mount a decrypted encs folder in a NTFS partition
2. Copy or move a file to that folder
3. A popup title 'Information - Dolphin' will appear and show the message 'could not change permissions for <path/filename>'



It's a popup per file and great clicking experience.
See also bug reports 196042 and 206500. (I don't know how to create links here, sorry)
Comment 1 Julian Steinmann 2018-05-15 19:01:03 UTC 
Can you still reproduce this issue with a newer version of Dolphin/KIO? If yes, this is most likely not a bug in Dolphin, but in KIO or even deeper down the stack. 

And btw, creating links to other bugs is really just writing the ID down directly after "bug": bug 196042 and bug 206500 :)
Comment 2 João Vidal da Silva 2018-05-16 10:30:55 UTC 
It's still happening with my current versions:
dolphin 18.04.0
kio 5.45.0

And thanks for the tip :)
Comment 3 Julian Steinmann 2018-05-17 09:33:35 UTC 
Okay, thanks for your response. I assume that this bug occurs in KIO, so I'll re-tag the report to their bug tracker. If anybody from the KIO team could take a look and tell us if this is actually a KIO bug that would be great.