update-manager suspends while performing dist-upgrade

[Timmie]

Binary package hint: update-manager

My Ubuntu laptop is set to suspend after 20min. idle time.

I tried to upgrade from Edgy Eft to Feisty Fawn via
System -> Administration -> Upgrade Management (update-manager). There I was told that a new version of Ubuntu was out and I choosed to upgrade to Feisty.

I went Away from the computer since the total download time was estimated to 3hrs.

After a while I checked back and the computer did suspend. I switched it on again and the laptop did not finish the upgrad. I restarted update-manager and it's now downloading the new applications and performing the upgrade.

To my thinking a computer shouldn't suspend while doing such a important task like a dist-upgrade.

The update-manager should either inform the unser to disable the suspend function while perfornimg the dist-upgrade or do this automatically.

I had the same problem when testing Feisty Beta on a desktop computer which is that old that it even doesn't support power management correctly. That pc just switched off while upgrading from Edgy to Feisty!

Thanks for addressing this!

[Timmie (timmie)]

Here's a screenshot that shows the stage of the upgrade process after the laptop was switched on again!

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are closing this report because you reported this bug a while ago and there is no recent duplicate nor user mentioning having the issue on Intrepid. If this is still an issue, don't hesitate to reopen the report. Thanks again!

[Timmie (timmie)]

Hello,
this occured also during the upgrade to 8.10.

[Jean-Baptiste Lallement (jibel)]

Thank you for following up. confirming because it can be reproduced with the latest release.

Thanks for your help to make Ubuntu better.

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #1046811, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.