do-release-upgrade stalled on "Setting up libgdu0 (2.32.1-0ubuntu4)" on Maverick->Natty upgrade

Bug #785848 reported by Boris Dušek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-disk-utility (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-disk-utility

1. Install Maverick i386 desktop (happened 3 months ago)
2. Update it to latest software using "apt-get update" and "apt-get dist-upgrade". I did not restart to boot into the new kernel.
3. Run "sudo do-release-upgrade" over ssh to upgrade to Natty. Answer "install new version" when promted what to do with the /etc/default/grub file

do-release-upgrade then ends up stalled on "Setting up libgdu0 (2.32.1-0ubuntu4)". In fact, it is then no longer possible to ping the machine's IP. I can't report what is the status of the machine since it's more than 200 km away.

I seem to not be the only one with exactly the same symptom: http://ubuntuforums.org/showthread.php?p=10811911

Boris Dušek (dusek)
description: updated
Revision history for this message
Paul Carter (pauleg-carter) wrote :

I 'm having failures during the first update after upgrade to 11.04 -

upgrade in 11.04 failed.
installArchives() failed:
Extract templates from packages: 81%

Extract templates from packages: 100%

Preconfiguring packages ...

(Reading database ... dpkg: unrecoverable fatal error, aborting:

 unable to open files list file for package `libgdu0': No such device or address

The /var/lib/dpkg/status file became corrupt in 2 places; discovered by running 'sudo dpkg --configure -a', which gave errors -

dpkg: error: parsing file '/var/lib/dpkg/status' near line 41429 package 'tracker-miner-evolution':
 field name `ple' must be followed by colon
 and after editing/repairing that -
dpkg: error: parsing file '/var/lib/dpkg/status' near line 73599 package 'pulseaudio-module-bluetooth':
 'Recommends' field, missing architecture name, or garbage where architecture name expected
After editing that one, the sudo dpkg --configure -a completed successfully.

Running update again generated the same kind of failure as before.

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.