Bug 114543

Summary: kget should complete a download by (retry connect) reconnect after every few mintues
Product: [Applications] kget Reporter: Mohd Asif Ali Rizwaan <maarizwan>
Component: generalAssignee: KGet bugs <kget-bugs-null>
Status: RESOLVED FIXED    
Severity: wishlist CC: mat69
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Mohd Asif Ali Rizwaan 2005-10-17 01:06:05 UTC
Version:           v0.8.5 (using KDE 3.4.92 (beta2, >= 20051010), compiled sources)
Compiler:          gcc version 3.3.4
OS:                Linux (i686) release 2.6.11.7

Why would we use a Download Manager? 
When the download is important and we want it safely and timely available. ex. KDE sources, openoffice, documents etc.

But kget when gets "connection error" (cannot connect to host) on a (an un-reliable) server, simply annoys by showing "Can't download from ..." popup-dialog.

over nfs (busy network) kget fail to save the file. so a retry would be a very good thing.

How to reproduce:
-----------------

1. download a big file say 100mb (openoffice or kdelibs so that we could get enough time to complete the next steps)

2. when the download starts wait for few seconds

3. disconnect the internet connection (ifconfig eth0 down or ifconfig ppp0 down or ifconfig wlan0 down or simply remove the cable)

4. Now Kget will prompt  that it can't download. 

5. And that's it, KGet will never try to download the file again :( which is very important to us.

6. Restore the internet connection.

7. Now we have to manually "Start" the download process for our important file.

Expected Behavior:
------------------

1. KGet should not use Popups (those are annoying, everybody hates it)
2. KGet should support "Retry delay" or "Retry connecting in <time>" say 1-5 minutes (configurable), so that a temporary disconnection does not stop our valuable file from getting downloaded.
Comment 1 Matthias Fuchs 2010-01-03 03:00:02 UTC
This bug should not happen in trunk (what will become 4.4) anymore thx to the changes of dario.

Sorry for the long delay and thanks for the report.