Feisty beta updater fails using fast unreliable net connection

term.log was empty

Does the updater still fail in Feisty Final?

I have no way of retesting this.

You could reinstall edgy and try to upgrade to Feisty Final.... but that is a lot of work.
I think one requirement for bugs is that they can be reproduced. So technically you can close this bug if you're not up for it. ;]

Generally reproducing one's own bugs is not good practise. This particular bug is a multiple factor bug and hard to reproduce from that point of view. Doesn't mean it's fixed even in head.

By this I mean, trying again since the final came out and you were trying to update to the beta -- the problem may be fixed. I once had a problem with OO.org icons while using compiz, I tried to reproduce the problem again but it wouldn't reappear, so I didn't file the bug.

Maybe you should have if only to see whether others had replicated your problem. Not being in your shoes I'm not certain whether it would be worth it.

With this one I went through the same process several times before resorting to the command line to fix it. Then I filed the bug. I've come across the "Sub-process gzip returned an error code" many times on Ubuntu at various times. The last time was today. It seems like quite some time since I've had to go to /var/lib/apt/lists and manually delete files to get the system on track again. That error seems to come from partially downloaded package lists or lists that appear to have downloaded properly but are corrupt.

You are right of course in that there could have been a major redesign in the code between beta and final which could have had the effect of fixing a bug as a side effect rather than by intent.

This bug seems unlikely to have been deal with, or be deal in the short term.
But does seems worth to be decided to keep or not, so confirming.

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, you are not using the most recent version of this package for your Ubuntu release. Please upgrade to the most recent version and let us know if you are still having this issue.

Paul, I marked this as incomplete because the report issue was not solved.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.