ubiquity (1.11.7) crash -- MigrationAssistantApply failed with code 2

[CambridgeRed]

Binary package hint: ubiquity

This report is about today's "jaunty daily image"
(20090211), specifically ubiquity's 1.11.7 version.

Here is the contents of the live session's file
/var/crash/_usr_lib_ubiquity_bin_ubiquity.0.crash
after I said "ubiquity --pdb" in a Terminal window
in the live session.

As you can see it said

   MigrationAssistantApply failed with code 2

whatever that means. Of course, I have no way of
knowing whether that is supposed to work, since it
is from a beta release, but in case it should have
worked here is a bug report.

Let me know if you need anything more. Thanks.

===================================================

[Evan (ev)]

I'm sorry, but the file you've attached does not contain enough detail for me to be able to determine the cause of this bug.

Can you please run the installer in debug mode (`ubiquity --debug` from a terminal window) and attach /var/log/syslog, /var/log/installer/debug, and /var/log/partman to this bug report?

Thanks!

[CambridgeRed (sj-02139)]

I will be happy to try it again, as you asked.

But I erased that CD-RW disk and also the
"daily" image I had burned onto it. Sigh.

So I went to download the current "daily"
image and discovered it is too big to fit on
a CDROM. Sigh again. So when I notice
it is small enough again I'll download it and
try it and let you know.

Thanks for being willing to look into it.

[Evan (ev)]

Thanks for your patience. :)

[CambridgeRed (sj-02139)]

I downloaded the 20090306 "jaunty daily image"
(with ubiquity's 1.11.15 version), burned it to a
CD-RW, booted into Ubuntu's "live" session, and
then said "ubiquity --debug" in a Terminal.

The first thing I want to report (let me know if
this should be filed as a separate bug report) is
that when the "Install" window then popped up I
could not see the bottom of it, just the warning
message. Thus I did not see the "Forward" button
(or anything else down there) and so was totally
unable to press it. And when I hit the "X" in the
upper-right corner, the installation aborted.

So I tried so increase my screen resolution. But
it was set to 800x600 and that was the highest
resolution on offer. I suspect the reason is that
I have an old monitor, without any "plug-and-play"
(DDC) capability, so your hardware could not
detect it and fell back to a default setting.

But I really think that ubiquity should be able to
cope with that -- not have dialogs too large to
fit into an 800x600 window. That was somewhat
annoying. (I don't recall it happening before,
when I just said "ubiquity --pdb" -- so maybe it's
new, or maybe it only happens with the "--debug"
switch -- or maybe my memory is just wrong.)

So I wasted a few hours trying to get around that.
If there is any standard solution it wasn't
obvious to a Ubuntu newcomer like me. Eventually
I ended up copying an /etc/X11/xorg.conf with a
higher resolution from a Fedora 9 installation I
had on another disk on that machine, installing it
as the Ubuntu live session's /etc/X11/xorg.conf,
then killing gdm and its children and restarting
gdm. That produced a live session desktop with a
higher resolution and when I then said "ubiquity
--debug" in a Terminal I could see all of the
resulting window. How inelegant. What a pain.

So I gave the same answers I usually give and made
the same choices I usually make, when I try to
install Ubuntu, and the installation went on until
the progress windows abruptly disappeared. It
only got as far as 88% ("Installing documents and
settings..." if I recall correctly).

(As another aside, let me mention that it is
annoying to have to sit there and wait until it
times out at various places. It seems like it
tries for about two minutes to set up an apt
repository, and then another two minutes while it
tries to set up a security repository, and then
more time (two minutes?) while it attempts to get
the time from an ntp server -- despite my hitting
the "skip" button, which has no obvious effect.
Since I have no Internet connection when I try to
install Ubuntu it would be nice if I could somehow
say so: a "skip" button which worked, say.)

So shortly another window popped up saying
"Application problem -- Sorry, the program
'ubiquity' closed unexpectedly ..." -- then I hit
the "Report Problem" button and waited while it
collected the information. Then I gathered up
/var/crash/_usr_lib_ubiquity_bin_ubiquity.0.crash
and /var/log/syslog and /var/log/partman and
/var/log/installer/debug, as you asked, and saved
them away out of the live session.

As you can see it still said

   MigrationAssistantApply failed with code 2

whatever that means.

So after submitting this initi...

[CambridgeRed (sj-02139)]

Perhaps it is the case that the migration assistant code
does not cover the case where it finds an existing linux
partition whose /home is only a mount point?

I would imagine that in such a case (an empty /home) it
should look in /etc/fstab to see if a /home entry is there,
then mount the corresponding partition and go on.

Just a guess. I don't mean to interfere. Thanks.

[Victor Vargas (kamus)]

Since this report have a long time without activity, could you check (if is possible) in latest version included in Karmic if this issue is still happening? Thanks in advance.

[Monkey (monkey-libre)]

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!

[Monkey (monkey-libre)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!