Bug 223068 - copy move operation bugs me with "Could not change permissions for $ntfs-filesystem/$filename"
Summary: copy move operation bugs me with "Could not change permissions for $ntfs-file...
Status: RESOLVED DUPLICATE of bug 206500
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-17 03:01 UTC by Mohd Asif Ali Rizwaan
Modified: 2010-01-17 18:08 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mohd Asif Ali Rizwaan 2010-01-17 03:01:10 UTC
Version:           1.4 (using 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1)), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.31-18-generic

I have ntfs partition for backup (to access it from both windows and linux using ntfs-3g).

But whenever I copy/move a file to ntfs partition using dolphin; it continuously complains about "Could not change permissions for
/media/Backup/readme.txt"

if I copy say a hundred files, i'll be annoyingly prompted with "Could not change permissions for xxx file"

I request that there should be a 
[x] Don't Ask this again (temp/permanent) option in the copy/move dialog, whenever the error occurs. 

thanks.
Comment 1 Mohd Asif Ali Rizwaan 2010-01-17 03:04:01 UTC
Not just the Popup dialog annoys; but the dialog also takes away the focus from dolphin window and hence Hampers my workflow.
Comment 2 Mohd Asif Ali Rizwaan 2010-01-17 03:10:17 UTC
It even complains when we try to copy a file from ntfs-3g partion to other. say from C:drive (/mnt/winc) to D:drive(/mnt/backup) using dolphin in linux. Whereas the cp command doesn't bother at all!

Expected Behavior:

1. Detect filesystem before applying/changing permissions.
2. Behave like cp command (which does *not* complain about could not change permission)
Comment 3 Frank Reininghaus 2010-01-17 18:08:39 UTC
Thanks for the report! This issue has been reported already.

*** This bug has been marked as a duplicate of bug 206500 ***