Bug 70911 - kget does not resume after interruption of connection on router
Summary: kget does not resume after interruption of connection on router
Status: RESOLVED FIXED
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-20 12:52 UTC by Woodhouse
Modified: 2005-07-26 13:35 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Woodhouse 2003-12-20 12:52:46 UTC
Version:           v0.8.3 (using KDE 3.1.94 (CVS >= 20031206), Gentoo)
Compiler:          gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice)
OS:          Linux (i686) release 2.4.22-ck1

Kget is not doing what it should as "download manager". 
When the connection is interupted on my firewall/router/server , kget says "stalled" for the interrupted download. It will not resume automatically, despite the fact that there is a setting that should take care of timeouts and retrying under "reconnect options". Manually pausing and and requeing DOES work however. The need of manual intervention defies the purpose of a dl manager in my opinion. This is mot most important thing it should do. The downloading PC is connected to a lan and accesses internet through a firewall/ server/ router,  running linux.

BTW. This Serious shortcoming of kget was already here in version 3.1.2 of kde. I thought it would have been dealt with in the kde 3.2 cvs i am running...;-)
Comment 1 Rainer Wirtz 2004-01-18 23:41:27 UTC
I can confirm this for kget 0.8.3 (kde 3.1.4, suse 9.0). Once a download is interrupted, it is marked as "delayed" and only resumed after manually "queued" again. The entries in "preferences->connection-tab->reconnecting options" are all set.
This is a dial-up connection.
Comment 2 Rainer Wirtz 2004-03-12 06:04:58 UTC
I have send in a patch that fixes this. Is in CVS now.
Comment 3 Urs Wolfer 2005-07-26 13:35:28 UTC
*** Bug has been marked as fixed ***.