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 613469 - Nautilus leaves broken file
Nautilus leaves broken file
Status: RESOLVED DUPLICATE of bug 389828
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.28.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-03-21 09:14 UTC by Oleksandr Redchuk
Modified: 2010-04-27 12:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Oleksandr Redchuk 2010-03-21 09:14:51 UTC
Nautilus 2.28.1 (2.28.1-0ubuntu3, Ubuntu Karmic Coala x86_64).

Iterrupted file copying/moving leaves broken file at destination folder.

Steps to reproduce:
Start the copying long file or directory with long files then interrupt copying by clicking on next to the progress bar "red X" button.
Nautilus silently leaves broken file at destination folder which hinders to complete the directory copy

Expected behavior:
Remove incomplete file chunk at destination folder and show warning
  or
Ask user for either of
- remove incomplete file
- finish current file copying than stops -useful for directory copying.
- left incomplete file as is but this option requires some kind of copying continuation, not only skip/overwrite
Comment 1 André Klapper 2010-03-27 16:05:29 UTC
Is this about local copying? Is this about the same partition?
Comment 2 Oleksandr Redchuk 2010-03-27 20:47:39 UTC
(In reply to comment #1)
> Is this about local copying? Is this about the same partition?

Local to local - some or different partition, local to USB drive (NTFS), network drive (smb://) to local - the same behavior.

Local to smb:// - all OK, no broken file on network storage.
Comment 3 Cosimo Cecchi 2010-04-27 12:38:56 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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