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 initial/additional report
I will attempt to attach the four files. But I
don't do that very often so I hope I get it right.
Let me know if you need anything more. Thanks.
--
ubiquity (1.11.7) crash -- MigrationAssistantApply failed with code 2
https://bugs.launchpad.net/bugs/328337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
