lack of meaningful dialogue box on a simple space problem when upgrading

[AwarenesS]

Binary package hint: update-manager

I upgraded from 8.04 to 8.10
At some point during the download it just failed to download the remaining packages. It only said "unable to download the package" or something general like that. Then it stopped and came back to the download "manager packages screen".

Then it said I could upgrade some packages (witch at that point I didnt know If it would be done as a part of the release update or just other kind of upgrade because I had new list of packages)

I knew I was running out of space, so I just freed some space and tried again. Then it all worked ok.

At no point I was advised I was running out of space to download the remaining packages

Hope its useful

[Chris Coulson (chrisccoulson)]

update-manager does a free space check before upgrading, so I think that the fact it worked after clearing up some space is just a red herring. This was probably a transient network problem.

Could you please attach all of the files under /var/log/dist-upgrade as separate attachments?

Thanks

[AwarenesS (voidplayer)]

I wish i could see anything meaningful in those files... because i dont :S

I tried the upgrade like 3 times... and then tried to free some space... and then it worked... I wasn't told that was the problem tho...

apt-term.log belongs to root. Do you need it too?

[Chris Coulson (chrisccoulson)]

Yes please. The apt-term.log is the one that will contain the most useful info.

Thanks

[Michael Vogt (mvo)]

The upgrade fails because of a problem with virtualbox-ose:

Preparando para reemplazar virtualbox-ose 1.5.6-dfsg-6ubuntu1 (usando .../virtualbox-ose_2.0.2-dfsg-0ubuntu3_i386.deb) ...^M
 * Shutting down VirtualBox host networking...^M
   ...done.^M
 * Stopping VirtualBox kernel module vboxdrv^M
   ...done.^M
dpkg: error al procesar /var/cache/apt/archives/virtualbox-ose_2.0.2-dfsg-0ubuntu3_i386.deb (--unpack):^M
 el subproceso pre-installation script devolvió el código de salida de error 1^M
 * Starting VirtualBox host networking...^M
   ...done.^M
 * Starting VirtualBox kernel module vboxdrv^M
   ...done.^M

I reassign.

[Michael Vogt (mvo)]

The log unfortunately overwrote the previous one (the one where the free space was a problem) so its hard for me to diagnose what went wrong. There is a freespace check in update-manager but it seems like it was not working properly in your case. How much free diskspace was needed in your case?

[AwarenesS (voidplayer)]

In my case it was needed about 1,5 Gb
The download stopped at 0,950 Gb or so. I susspected of the free space because i knew i was running out of space.. I knew I had about 1Gb left..

Sorry I overwrote the log file, i didnt know where to look. Maybe it should keep all the logs instead of overwriting when its in alpha :)

Next time ill cach it red handed ;)

[Michele Mangili (mangilimic)]

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!