Hi Colin, I thought the visual.d scripts present, *and manipulate* an in memory view of partitions, which are later checked by check.d, and then written to disk by commit.d. If it isn't visual.d, then what manipulates the partitions? The problem seems to be that ubiquity is running init.d -> visual.d ( which manipulates the in memory partition tables ), then runs init.d *again* and they aren't designed to be run a second time.
-- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
