Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
The Ubuntu community has contributed 21986 ideas, 135057 comments, 2615221 votes
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas
Idea #28648: Copy process pauses/interrupts on file conflict

Written by komputes the 8 Oct 11 at 17:59. Related project: Nautilus. Status: New
Rationale
Copy process pauses/interrupts on file conflict. Ideally we would want all file conflicts would be managed before the copy starts and not during the copy.

216
votes
up equal down
Solution #2: Continue copying the files that doesn't need confirmation
Written by komputes the 8 Oct 11 at 19:12.
Solution #17: Continue copying the files that doesn't need confirmation

Written by pgdx the 31 Jul 09 at 08:09.
The copying of the rest of the files should continue and the files in question should be queued until the user decides what to do with this.

Need brainstorm admin help with import solution 17 from here:
http://brainstorm.ubuntu.com/idea/15427/
-17
votes
up equal down
Solution #3: Before copy start batch process list of conflict need to be displayed
Written by benoyanthony the 11 Oct 11 at 12:57.
Before copy start batch process list of conflict need to be fisplayed in the box and then user can be given option agains each file for overwrite, duplicate, skip , etc.
-8
votes
up equal down
Solution #4: Before copy start batch process, choices can be made
Written by ianp5a the 28 Oct 11 at 06:46.
(similar to #3)
An 'option' to let the user set what should be done for each conflict at the 'start' of the process.
The user intends to leave a long copy process unattended, and expects it to be finished upon their return. In this case the user 'knows' there will be overwrite errors and 'knows' what they want to be done in those cases.
This is important by long copies. Eg slow Networks and hundreds of files and folders.
This option could be on a button on the correct part of the "File Operations" Dialog. That means the copy is already running when the choices are made. Regardless of if an error have already occurred.
This solution solves this common case and does not conflict with other solutions that may be required.

Propose your solution

Attachments
No attachments.


Duplicates


Comments
komputes (Brainstorm moderator) wrote on the 10 Oct 11 at 15:57
https://bugs.launchpad.net/nautilus/+bug/871492
https://bugzilla.gnome.org/show_bug.cgi?id=339420

PaddyLandau wrote on the 11 Oct 11 at 14:57
Solution #3: Nice idea, but the problem is that the file system can change while awaiting the user's response.

wrigleyster wrote on the 14 Oct 11 at 23:44
Solution #2: If the list of files in conflict was saveable at the end, it would be ideal.

petko10 wrote on the 22 Oct 11 at 21:53
Such conflicts appear mostly when there's something wrong with the copying in general and are sometimes useful not to mess things up too much when pasting or copying to a folder with many files where you won't be able to pick the new files out easily . So I think the current system is not bad . Is it allowed to post a solution "Leave it be" ?

HDave wrote on the 5 Mar 12 at 14:20
Just realize that when dealing with mutli-user file servers, you could start a copy operation which expects no conflicts and then one could be created AFTER the copy operations starts. Thus the current system behavior cannot be eliminated, only augmented.

mikk0 wrote on the 1 May 12 at 06:37
Yesterday copied a user's home directory over samba network to her new computer. File's with names like "Artist: song", or "Gorgeous


Post your comment