migration assistant crash with code 2

Bug #326398 reported by Mark Falcey
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Jaunty alpha 3 and alpha 4 amd64 live CD iso

migration assistant crashes manual install. No migrations assistant selection page appears during manual install so it is impossible to bypass or control migration settings. I have multiple OSs with multiple users on multiple hard drives on this machine. I do not want to migrate anything to this install but apparently am not given any choice in this. This is not a good situation.

I uploaded a crash report but I am not sure if it got through. This is an improvement over jaunty a3 which crashed in the exact same manner but trying to send the crash report gave a time out error.

As a result of the crash ubiquity exits and grub is not installed.

I have attached the /var/log/user.log which includes the traceback

Revision history for this message
Mark Falcey (mfalcey) wrote :
Revision history for this message
doc_471 (the-analist-3d) wrote :

I can confirm this bug.

The Ubiquity installer crashed with code 2 while performing the MigrationAssistantApply Task, line 1334 in configure_ma of the /usr/share/ubiquity/install.py file.

This event happened while using the Jaunty final release Live CD environment, 32-bit version.

Revision history for this message
Monkey (monkey-libre) 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. It would help us a lot if you could test a current, supported, Ubuntu version. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 326398, and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Monkey (monkey-libre) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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