Comment 1 for bug 146866

This didn't get reported in quite the way I'd intended -- the AppPort report happened to come to my attention just after I'd done something else to cause something to crash and I initially thought this would be that crash report. Nonetheless, I feel this report still has some merit even if the description isn't quite right.

I ran "upgrade-manager -c -d" just before I went to bed, thinking it would take several hours to download all the new packages and I'd continue in the morning. I disabled the screensaver and so on, so no extra processes would be running during the upgrade. However, when I came to complete the upgrade the following morning, gcc-4.2 was one of many packages that apparently could not be installed. I didn't take a note of all the failed packages as there were so many, but I did have to spend a couple of hours cleaning things up in an interactive aptitude session for the apt caches to clear themselves up and the upgrade to complete.

The only thing that occurred to me was that I do have a cron job to automatically download updates each morning -- but I expect most if not all Ubuntu users also do, and I'd be surprised if I were the only person to leave the upgrade running overnight.

Now the upgrade has completed I'm very happy with the beta release, but something certainly went amiss with the upgrade process. Are there any logs I can provide that might help discover what?