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

[Mathieu Trudel-Lapierre]

I think we've established the most common cases for this are fixed; so
I'll close this as Fix Released -- ubiquity will properly handle blank
drives.

Fixes landed in:

 - partman-auto: https://launchpad.net/ubuntu/+source/partman-auto/125ubuntu2
 - ubiquity: https://launchpad.net/ubuntu/+source/ubiquity/2.21.22

One remaining issue will be to properly deal with "user errors", that
is, running manual partitioning but not creating an EFI partition while
booted in EFI mode.

Phillip, can you open up bugs for the issues you noticed so we can track
them appropriately?

** Changed in: partman-auto (Ubuntu)
       Status: In Progress => Fix Released

** Changed in: ubiquity (Ubuntu)
       Status: In Progress => Fix Released

-- 
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:
  Fix Released
Status in partman-efi package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Fix Released

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