After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 693528 - Canceled copy/move operations should not left incomplete files
Canceled copy/move operations should not left incomplete files
Status: RESOLVED DUPLICATE of bug 403652
Product: nautilus
Classification: Core
Component: File and Folder Operations
3.6.x
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-02-10 15:35 UTC by Dario Ruellan
Modified: 2013-03-17 17:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dario Ruellan 2013-02-10 15:35:17 UTC
When the copying of a file is interrupted (by the user or by some error) an
incomplete file is left of the target folder. It is not possible to detect that
this file is incomplete at first glance.

Test case:
 - Open Nautilus
 - Open a second folder on a tab
 - Copy/move a big file form one tab to another
 - Cancel the transfer using the X button.

The unfinished file remains on the destination folder, now, since this file is incomplete (possibly unusable) and the user directly stated that he/she did not want to transfer this file, seems wiser to remove the incomplete file.

If for some reason is not possible to delete the incomplete file, Nautilus should have a mechanism to inform the user the file is not complete (ex: adding an extra extension to the filename).

See also: https://bugs.launchpad.net/hundredpapercuts/+bug/1072135
2.6.x branch report: https://bugzilla.gnome.org/show_bug.cgi?id=403652
Comment 1 António Fernandes 2013-03-17 17:54:33 UTC
Thanks for letting us know this still happens. If this is the same as bug 403652, it's better to track this in a single report. I'll update the version in the other report.

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