| Summary: | odd permissions when copy file from CD | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Salvo "LtWorf" Tomaselli <tiposchi> |
| Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | kdelibs-bugs-null, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.47.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Salvo "LtWorf" Tomaselli
2015-10-05 07:40:48 UTC
umask doesn't matter because these aren't new files, they are the result of a copy. Basically KIO emulates `cp -a`, i.e. preserves permissions. cp has command line options to choose whether to preserve or not, drag-n-drop doesn't ;) So it's tricky to guess what the user wants. In your case you obviously didn't want readonly files, but in general, preserving permissions when copying is seen as a feature rather than a bug. So I'm not sure how to "magically make it right for everyone in all cases". Maybe it is possible to find out if the source file system is mounted "read-only", resulting in all files to have the "read-only" attribute. |