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 333730 - Support for pause and resume for file operations.
Support for pause and resume for file operations.
Status: RESOLVED DUPLICATE of bug 124783
Product: nautilus
Classification: Core
Component: File and Folder Operations
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 337772 448424 558006 569570 583034 587971 595768 596791 603166 615092 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-03-07 10:31 UTC by Dominique Hazaël-Massieux
Modified: 2012-08-15 12:08 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Dominique Hazaël-Massieux 2006-03-07 10:31:43 UTC
When a copy (or move) operation takes a long time, a window offers to cancel the
operation; it would be very useful if there was also an option to "pause" the
operation (the same way one can pause a download e.g. in firefox), esp. when
over a network connection (e.g. ftp).

I assume there are also cases where this may prove useful for local operations
as well (e.g. to reduce temporarily the disk activity when more than one process
needs a high IO throughput).
Comment 1 Jan Arne Petersen 2006-08-25 20:58:06 UTC
*** Bug 337772 has been marked as a duplicate of this bug. ***
Comment 2 Thomas Hecker 2007-11-21 11:42:14 UTC
I mean this is a _very_ big improvement and advantage compared to other OS. Why there isn't any feedback on this enhancement?
Comment 3 Tshepang Lekhonkhobe 2008-02-06 08:16:16 UTC
This is among my biggest gripes about the all-important Nautilus...
Comment 4 Mårten Woxberg 2008-02-09 13:53:01 UTC
In the new gvfs there's a cancel button besides each copy/move process.
There should be a pause button there as well.
That way I could stack up my copy/move operations and then press pause on those who can wait.

This is especially good when copying lots of large files where the seek time slows the copying down if you copy multiple files.
Comment 5 Cosimo Cecchi 2008-04-14 12:32:56 UTC
*** Bug 448424 has been marked as a duplicate of this bug. ***
Comment 6 Tshepang Lekhonkhobe 2008-04-14 18:10:54 UTC
Cosimo: Why is 448424 marked as duplicate? These are separate issues, even if similar. Instead you should have merely stated that the two bugs are related (or is that the point of the dup)? To me, a patch that fixes 448424 would be a nice enhancement to a patch that fixes 333730, but they simply aren't the same.
Comment 7 Cosimo Cecchi 2008-10-27 10:00:54 UTC
*** Bug 558006 has been marked as a duplicate of this bug. ***
Comment 8 Mårten Woxberg 2008-10-27 10:14:06 UTC
In Windows Vista I use TeraCopy to copy my files (it replaces normal copy/paste),
and that program detects if it has multiple copy operations going and waits to start them until the first one is finished.

That way I can stack files I want to copy and they will be copied at full speed one batch (I can select 1 or several files and that counts as a job) at a time.
If I want to start a process before the other is finished I just press the start copy button and it'll work as normal. This is a big improvement over normal copy paste behaviour. 

TeraCopy also does what Bug 448424 was talking about, it resumes files.
Comment 9 Cosimo Cecchi 2009-01-30 11:20:48 UTC
*** Bug 569570 has been marked as a duplicate of this bug. ***
Comment 10 Joel Goguen 2009-01-30 11:46:47 UTC
Something similar to this has also been requested by an Ubuntu user.  The Launchpad bug is at https://launchpad.net/bugs/315423.

Currently Nautilus can copy to FTP and other remote servers, but it could use
improvements.  For example, if I copy a file to a FTP server and the server
closes connection, or my network has an error, the copy process is aborted.  It
would be nice if unsuccessful transfers could be shown with the option to abort
or retry them.  The option, for all transfers, to pause and limit transfer
speed would also be nice.
Comment 11 Cosimo Cecchi 2009-07-08 10:44:32 UTC
*** Bug 587971 has been marked as a duplicate of this bug. ***
Comment 12 Cosimo Cecchi 2009-09-30 14:24:30 UTC
*** Bug 596791 has been marked as a duplicate of this bug. ***
Comment 13 A. Walton 2010-04-07 19:11:56 UTC
*** Bug 615092 has been marked as a duplicate of this bug. ***
Comment 14 Cosimo Cecchi 2010-04-27 13:02:37 UTC
*** Bug 603166 has been marked as a duplicate of this bug. ***
Comment 15 Mårten Woxberg 2010-04-27 13:14:57 UTC
Actually Bug 603166 is not a duplicate of this bug.

This bug only handles the Pause/Resume feature.
Bug 603166 is a bug about Canceling the Copying leavs a partial file on the drive.
Comment 16 Cosimo Cecchi 2010-04-27 13:23:07 UTC
Bug 603166 is about both, but what you said is bug 389828 anyway.
Comment 17 Cosimo Cecchi 2010-08-01 16:26:15 UTC
*** Bug 595768 has been marked as a duplicate of this bug. ***
Comment 18 Cosimo Cecchi 2010-12-18 01:54:06 UTC
*** Bug 583034 has been marked as a duplicate of this bug. ***
Comment 19 Felix 2011-02-15 06:33:31 UTC
Pause+resume file transfers (copy, cut, delete)
KDE has this feature for years now. Please add it to nautilus copy dialog also.
Comment 20 Constantine Nosovsky 2011-04-04 16:11:28 UTC
Not as simple as it seems.
As far as I can see looking at Nautilus source code file transfers use GIOSchedulerJob which is run asynchronously and uses threads if they are available, so it's OK to make the thread sleep, but the GIO API doesn't provide such methods. How about 3.0 version?
It may be useful to allow user control priority of the IO job at least.
Comment 21 William Jon McCann 2012-08-14 22:26:13 UTC

*** This bug has been marked as a duplicate of bug 124783 ***
Comment 22 Mårten Woxberg 2012-08-15 06:24:10 UTC
How is this a duplicate of bug 124783 ??? Nowhere in that bug does it say anything about Pause/Resume of copying.

I agree they are connected but it's definately not the same bug.