Comment 22 for bug 145712

When I boot the Live-CD with Hardy Heron I don't have Nautilus opening up windows showing my home page or external USB hard drive. Your having a unique problem as well as I am.

----- Original Message ----
From: John S. Gruber <email address hidden>
To: <email address hidden>
Sent: Friday, March 28, 2008 3:32:15 PM
Subject: [Bug 145712] Re: Gutsy beta - Desktop CD install hangs on migration screen

I seem to be having the same problem with the Hardy beta (+) live-
install CD. I can free up the system by unmounting all (or some) of the
partitions left mounted by os-prober and migration-assistant. When I run
with --debug the problem doesn't occur. I suspected the mounts as
multiple devices were left mounted on the same mount points. I have a
hunch that a race condition is involved somehow, but I don't know that.

The system doesn't hang if I specify --no-migration-assistant, run with
--debug,don't mark a windows partion at hda6 as don't use, or mount all
partitions to appropriate different /media/hdxx mount points before
hand. I tried this last idea realizing that running ubiquity under an
installed gutsy system wasn't hanging and the mounts remaining after
running it weren't as funky.

migration-assistant leaves out partitions in its survey of users available for migration. Which ones it
leaves out and leaves in are difficult to predict. Sometimes it says none are available and sometimes it
lists most (from 1 ntfs partition (hda1) and 4 ext3 partitions (hda5, hdb2/6, hdb7/8, hdb9). Rarely are all partitions represented. The last userid of hdb9 is often left out, but that may be a different problem.

As ubiquity is running gnome file explorers pointing to partitions start
up on their own, I suspect as partitions are mounted by ubiquity
components.

I can get around all of this. I'm submitting this report to provide feedback on Hardy beta. Please advise if
I can do anything helpful.

--
Gutsy beta - Desktop CD install hangs on migration screen
https://bugs.launchpad.net/bugs/145712
You received this bug notification because you are a direct subscriber
of the bug.