Bug 306420 - No resume after volume full condition
Summary: No resume after volume full condition
Status: RESOLVED WORKSFORME
Alias: None
Product: kget
Classification: Applications
Component: Core (show other bugs)
Version: 2.7.0
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: KGet authors
URL: http://download.opensuse.org/distribu...
Keywords:
Depends on: 430792
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-07 19:55 UTC by Christopher Yeleighton
Modified: 2020-12-24 16:08 UTC (History)
1 user (show)

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 Christopher Yeleighton 2012-09-07 19:55:38 UTC
KGet cannot recover from a volume full condition.  Once it stops downloading, it does not download until it is restarted.

Reproducible: Always

Steps to Reproduce:
  1.  Tell KGet to download to a volume that is almost full.
  2. Make enough room on the target volume.
  3. Tell KGet to resume downloading.
Actual Results:  
  1. KGet stops downloading at 88%.
  3. KGet says download is running and suspended (no data arrives).

Expected Results:  
  3. Let KGet resume downloading.

Workaround: restart KGet.
Comment 1 Christopher Yeleighton 2012-09-07 19:56:56 UTC
Version: 2.7.2
Comment 2 Andrew Crouthamel 2018-11-09 01:08:02 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-20 03:58:26 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:41:21 UTC
Thanks for the report Christopher however I believe this is now resolved as kget pre-allocates data on the destination now.

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:59 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:48 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!