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.
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.