ubiquity crashed on amd64/mac during post-install configuration

Bug #742850 reported by Chad A Davis
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Installing live CD (ubiquity) from Natty dev. branch (2011-03-23). Enabled 3rd party software and updates during install. Ubiquity went through the install and then identified it's own crash, advising to submit this bug report.

syslog shows that dpkg had problems configuring man-db and with jockey's DriverDB cache. I cannot determine which, if any, of these two was the cause for the crash.

grub had not yet gotten to installing itself. So the system could not be booted.

plugininstall.py also threw an exception:

 DebconfError: (10, "oem-config/enable doesn't exist")

/var/crash contained no other crash reports.

This is ubiquity 2.5.27 on a MacBook Pro 6.2. I had installed successfully via the alternate CD with the Natty dev. branch from one week earlier. I.e it is possible to install Natty on this machine, but I hadn't tried it with ubiquity previously.

I'm retrying the install without updates or 3rd party software.

Tags: amd64 natty
Revision history for this message
Chad A Davis (chadadavis) wrote :
Revision history for this message
Chad A Davis (chadadavis) wrote :
Revision history for this message
Chad A Davis (chadadavis) wrote :

The same install succeeded when I selected neither 'updates' nor 'third party' software. After rebooting I was able to subsequently install all the same updates with no issues.

Revision history for this message
Chad A Davis (chadadavis) wrote :

This may have been the result of a 'partial upgrade' being required.

Is ubiquity still capable of handling 'updates during install' if those updates would normally require a 'partial upgrade' ?

I've only be able to recreate the issue with the Mac install ISO (amd64+mac) so far.

Revision history for this message
Colin Watson (cjwatson) wrote :

Thanks for your report. This is also bug 739632, recently fixed.

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.