Upgrade tool didn't run normally, system may be unstable

Bug #173557 reported by Joe Bradley
2
Affects Status Importance Assigned to Milestone
release-upgrader-apt (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I have a Fiesty Fawn installation on an AMD64 machine that I attempted to upgrade to Gusty Gibbon. While running, I got a series of errors. In particular, it told me it could not install several packages because of a missing library, including:

bash
login
passwd
sudo
and a bunch of gnome packages (maybe a dozen).

During installation I got the message " The upgrade aborts now. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a).", after which the installer went about its business. At the end it directed me to open a bug and attach the contents of /var/log/dist-update, which I am now doing.

At this point, my system seems to be stable and many things seem to have been upgraded, but I have no clue what to do next. Some of the packages it reported as having problems are pretty basic, and I'm afraid to reboot lest on the reboot I don't have a working machine.

Please indicate what the next step I should do is. Logs are attached. Thanks very much.

Revision history for this message
Joe Bradley (joe-bradley) wrote :
Revision history for this message
Joe Bradley (joe-bradley) wrote :
Revision history for this message
Joe Bradley (joe-bradley) wrote :
Revision history for this message
Joe Bradley (joe-bradley) wrote :
Revision history for this message
Joe Bradley (joe-bradley) wrote :

An update, for whoever is watching this.

After having done basically nothing to remediate the situation, my system has been running fine, and shows no stability problems. So either the installation repaired itself after updates/reboots, or there was never a problem to begin with. The problems I did have after the upgrade were the minor one normally gets on a kernel update, similar in nature to when I upgraded from Edgy to Feisty.

So I don't know what the issue was on the install that it complained so loudly about. The logs, which I attached when I file the bug, will tell you more than I know about it.

Revision history for this message
J. Austin Rodriguez (jeanaustinr) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

Changed in release-upgrader-apt (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.