(*** This bug was imported into bugs.kde.org ***) Package: kfile Version: unbekannt (using KDE 2.2.0 beta1) Severity: wishlist Installed from: SuSE Compiler: gcc version 2.95.2 19991024 (release) OS: Linux (i686) release 2.4.6 OS/Compiler notes: I've had this some time now that I download a rather big file (linux kernel kde rpm's ;-) which are bigger than the space left on device. All choices which are available on the upcomming dialog result in dismissing the currently downloaded file. I'd suggest a button named "Try again" or "Continue" which allows you to free up some space and continue downloading the file. In addition the file size is often known before the file has to be downloaded (header info). It would be nice if the user could be informed before downloading if the file size exceeds the available disk space. (Submitted via bugs.kde.org) (Called from KBugReport dialog)
*** Bug 41109 has been marked as a duplicate of this bug. ***
*** Bug 119925 has been marked as a duplicate of this bug. ***
this bug is 5 years old and needs to be fixed. is this only a problem with http downloads or is it a problem with ftp and fish and other transactions?
It seems that the behaviour changed. I'm using 3.5.2 and I tried fish, NFS, http and ftp. The result was always the same: > Could not write file foo. > Disk full. Without any real choice. It's just the confirmation that the download was aborted.
Same problem with Konqueror as an "ftp file manager". When downloading some stuff, from the website (ftp) to my computer, for some reason the communication between the two computers might not be perfect. And that's when a copy error occurs. But there is no "Retry" button. If I try again, to download these files, separately, the download process works fine. It's obvious that the "copy error" occurs because of some TEMPORARY communication failure. Therefore we desperately need the "Retry" button. Additionally it's not possible to copy the error message, to note down, which files need to be "re-downloaded", but that is another bug.
*** This bug has been confirmed by popular vote. ***
http://quickgit.kde.org/?p=kdelibs.git&a=commit&h=cce47cb3ad4385cd2ac22b1039a7b5347419a4f9