Bug 278686 - KGet shows wrong info about downloading state on unstable connection
Summary: KGet shows wrong info about downloading state on unstable connection
Status: RESOLVED WORKSFORME
Alias: None
Product: kget
Classification: Applications
Component: UI (show other bugs)
Version: 2.2.4
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-28 09:37 UTC by Constantin Dolinin
Modified: 2020-12-24 04:34 UTC (History)
2 users (show)

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


Attachments
Screenshot with bug (116.54 KB, image/png)
2011-07-28 09:37 UTC, Constantin Dolinin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Constantin Dolinin 2011-07-28 09:37:14 UTC
Created attachment 62264 [details]
Screenshot with bug

Version:           2.2.4 (using KDE 4.6.2) 
OS:                Linux

When I have a very slow and unstable internet connection and downloading have more interruptes, KGet show wrong info about downloading state - you can seen it on attached screenshot.
Same in Russian, my native language:
Когда у меня очень медленное и нестабильное подключение к Интернету и когда закачка постоянно прерывается, KGet показывает неверную информацию о статусе закачки - вы можете увидеть это на приложенном скриншоте.

Reproducible: Didn't try

Steps to Reproduce:
1. Do your connection to the Internet a very sow and unstable.
2. Start downloading in KGet, more 5 MB
3. Wait for 100% and look for

Actual Results:  
1. In window header persents go to more 100% (103%, for example)
2. downloaded mbytes > filesize
3. and more...

Expected Results:  
shows right and works good

OS: Linux (i686) release 2.6.38-10-generic
Compiler: cc
Comment 1 Matthias Fuchs 2011-08-04 15:02:52 UTC
So the download stays at running while it finished already?

The >100% is clearly a bug.

Though the downloaded bytes being larger than the filesize is not a bug as sometimes you actually have to download parts you already got if the connection is very unstable. Probably the code could use some improvments there too.
Comment 2 Andrew Crouthamel 2018-11-06 15:19:03 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-18 03:31:39 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2020-11-24 02:47:47 UTC
Thanks for the report, Constantin.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 5 Bug Janitor Service 2020-12-09 04:33:57 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2020-12-24 04:34:45 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!