Bug 310943 - Better handling than 'Could Not Write: Disk Full'
Summary: Better handling than 'Could Not Write: Disk Full'
Status: RESOLVED DUPLICATE of bug 245597
Alias: None
Product: kio
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 4.9.3
Platform: Debian unstable Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-30 18:15 UTC by Jeffrey
Modified: 2014-08-08 08:58 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey 2012-11-30 18:15:02 UTC
Copying files from one drive to another, if the destination drive fills up KDE stops copying.  I don't know where it stops, what isn't copied, etc.

I'd really like to resume this copying after making space available.  I assume the behaviour is the same for moving files.

Reproducible: Always

Steps to Reproduce:
1. Copy music files to phone or other drive
2. Destination drive fills up
3. Missing files are unknown; I have to restart the copy process
Actual Results:  
Copying stops, I have to start over after freeing up space.

Expected Results:  
Copy/move is put on pause and gives me the chance to free up space and resume to copying

Reassign to KIO or whatever if required.  Thanks for KDE!
Comment 1 Frank Reininghaus 2012-12-02 18:12:45 UTC
Thanks for the report! KIO looks indeed like the right product for this because this is where copying and moving files is handled.

Moreover, I'd say that this is more a wishlist item than a bug because stopping the copying process if the target device is full looks like a valid reaction to me, even though I agree that a way to resume the process once some space is freed would be nice.
Comment 2 Frank Reininghaus 2014-08-08 08:58:56 UTC

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