So my earlier analysis on this bug was correct, as evidenced by the new
bug #1547286. The real underlying problem is still that the init.d
scripts are executing *after* the commit.d scripts have written the
partitions to the disk, and they are not intended to. Matthie's attempt
at fixing this worked around the problem by allowing the script to see
the newly created ESP so it concludes that there is already an EFI
booting OS installed on the disk and does not complain. This isn't
really true, but it at least stops the warning. In the case of this new
bug, no ESP was created, and so the init.d script still erroneously
concludes that some non EFI booting OS is already installed and the
broken message pops up and hangs the install.
** Changed in: partman-auto (Ubuntu)
Status: Fix Released => Triaged
** Changed in: ubiquity (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1418706
Title:
Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode
install
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1418706/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
