Ubuntu
ubiquity package

  1. Bug #235794
  2. Comment #7

Comment 7 for bug 235794

Revision history for this message
D. Hugh Redelmeier (hugh-mimosa) wrote :

I've experienced this problem installing 8.04.1 on a Dell Inspiron 6000 notebook. This was repeatable. It also happened when I fell back to installing 8.04.

Should I create a new bug entry because this is Hardy?

To recap:

- I do a fresh install on this notebook.

- I do the partitioning: this is going to replace Fedora Core 4 and co-exist with Fedora Core 6. There is also a never-run WinXP installation partition (i.e. it isn't WinXP, but if it were run, it would install WinXP; as delivered by Dell).

- the installation runs to ~90% and then disappears from the desktop as if finished (except we know that that isn't how an installation finishes).

- the resulting system is unbootable: grub is not installed, no initrd is installed, no /boot/grub/menu.lst. This, in fact, is how I discovered something was wrong the first time: I didn't notice that the silent termination was in fact a failure.

As requested above, I did an installation run after installing "set -x" after the first line of two shell scripts /usr/lib/ubiquity/migration-assistant/ma-ask and /usr/lib/ubiquity/migration-assistant/ma-apply

Based on reading the tealeaves in the resulting /var/log/syslog, I decided to hide Fedora Core 6's fstab (I renamed it /etc/fstab.HIDE) and then the 8.04.1 installation worked.

As I type this report, I no longer have access to the notebook. I don't have a copy of the fstab. Perhaps the only odd thing was that I had commented out the last line since it referred to the partition that I was taking over for Ubuntu's /home. That line started with #LABEL=/space, I believe.