Bug 165354 - download sometimes not finished on 100%
Summary: download sometimes not finished on 100%
Status: RESOLVED FIXED
Alias: None
Product: kget
Classification: Applications
Component: Multisegkio (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2008-06-29 19:59 UTC by Konstantin
Modified: 2018-09-19 14:31 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin 2008-06-29 19:59:49 UTC 
Version:           2.0.3 (using 4.0.5 (KDE 4.0.5), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-19-generic

download sometimes not finished on 100%, not disconnected and starts again
Comment 1 Urs Wolfer 2008-06-29 20:38:27 UTC 
Can you please provide a sample download link which does not work for you? Does it always happen this way?
Comment 2 Konstantin 2008-06-29 20:41:31 UTC 
It can be from every link, but if I start download after deleting previous (from the same link), it work normally...
Comment 3 Diogo Nardelli Siebert 2008-07-17 22:23:58 UTC 
It happens here too. That I remenber it happens with rapidshare links and i think is releated with resume downloads from a previous section.
Comment 4 Diogo Nardelli Siebert 2008-07-20 01:19:29 UTC 
I made some tests here. This bug happens when we set more than one thread in the multithread plugin. Kget don't set the download as finished, altough the download is 100%,  when you pause the download and exit kget and continue the download later. Sorry for the bad english.
Comment 5 Lukas Appelhans 2008-09-14 14:55:50 UTC 
Ok this is either a bug in MultiSegKIO or KIO itself...

Lukas
Comment 6 Lukas Appelhans 2008-11-16 15:27:08 UTC 
Can someone retest this? Should be fixed in latest trunk...

Lukas
Comment 7 Matthias Fuchs 2009-09-11 17:51:13 UTC 
Please retest with current trunk.
Comment 8 Andrew Crouthamel 2018-09-19 14:31:27 UTC 
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.