[Bug 1418706] Re: Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode install

[Phillip Susi]

In other words, the init.d scripts are supposed to be the first ones
run, so they can look at the state of the drive as it is when you first
boot the installer.  Instead, ubiquity is running the visual.d scripts
first, so they decide to add an efi system partition, and then ubiquity
runs the init.d scripts after that, so they see the ( partially created
) new partition.

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

Title:
  Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode
  install

Status in partman-auto package in Ubuntu:
  In Progress
Status in partman-efi package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress

Bug description:
  When doing a UEFI-mode install using the latest daily Vivid ISO (Thu
  Feb 5), Ubiquity incorrectly concludes that a blank drive contains an
  existing BIOS-mode install (see error in attached screenshot).

  The resulting error dialog is also broken: none of the buttons do any
  thing when clicked: X (close button), "Go Back", "Continue".

  You can seemingly move the install forward by clicking "Continue" in
  the main installer window, but things are still broken somewhere as
  grub isn't getting correctly installed (system is unbootable after the
  install completes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1418706/+subscriptions