[Bug 1042930] Re: partition size error during install of Quantal on Panda board

[Nicholas Skaggs]

@Oliver, I personally always used USB to install to for the same reasons
you mentioned above. However, in general the preference seems to be
geared towards installing to the SD, hence the instructions on the wiki
for doing so. If we don't wish to support this type of installation,
let's make the decision and setup the docs and tests to reflect that
properly.

FYI, I believe the preference for using the SD card itself was that the
pandaboard only has 2 usb ports, and thus a hub is recommended if your
installing to a USB drive. But others would have to comment on the
specifics.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1042930

Title:
  partition size error during install of Quantal on Panda board

Status in “ubiquity” package in Ubuntu:
  Confirmed

Bug description:
  I was testing using this image: http://cdimage.ubuntu.com/daily-live/20120828.2/quantal-desktop-armhf+omap4.img on a Panda board, I was trying to install to a partition created on a SD card with Gparted  (see these instructions: https://wiki.ubuntu.com/ARM/QA/Pandaboard).
  On the "installation type" window, were you have to select the partition on which to install, I selected the already created ext2 partition previously created on the SD card with gparted, I chose ext2 as filesystem type and / as mount point, when I confirmed, got a message window saying that "Before you can select a new partition size, any prevoius changes have to be written to disk..." (see attached picture).
  I then clicked on "go back" (I did not change the partition size), ubiquity went back to the "installation type" window.
  I clicked on the "install now" button as I saw that the ext2 partition was selected for install as root partition, but got an error message window and Apport took me to the already reported  bug #727842 in firefox, but could not do anything to mark it as affecting me as the bug must be a private one and do not have permission to.
  After this could not do anything else, selecting reboot or switchoff did not do anything, CTRL+ALT+F1 did nothing, CTRL+ALT+CANC made me reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1042930/+subscriptions