oem-config missing from installed system after OEM mode setup using EFI boot

[Max Bowsher]

Scenario: d-i EFI netboot with oem-config/enable=true

Problem: After the install completes and reboots into the OEM configuration temporary user, there is no icon on the desktop to invoke oem-config-prepare - indeed, oem-config is not even installed.

Cause: oem-config-udeb installs a finish-install.d script which runs 'apt-install oem-config-gtk ubiquity-frontend-gtk', however this fails. It turns out to be a dependency issue. ubiquity depends on 'grub-pc | grub | grub-efi', however grub-efi is now a dummy transitional package and is not installed (the actual package is grub-efi-amd64). The APT resolver makes a bad choice, and tries to install grub-pc (the BIOS boot version), uninstalling the EFI version. This fails, leaving oem-config not installed.

An adequate (if somewhat inelegant) solution should be to replace grub-efi in ubiquities dependencies with all possible platform varieties of grub-efi-<ARCH>.

[Cam Scott (cam-scott)]

I am seeing the same problem on servers with a UEFI BIOS and on virtualbox VMs when EFI is enabled in System->Motherboard->Extended Features.
Tested with ubuntu-12.04.5-server-amd64.iso and ubuntu-14.04.2-server-amd64.iso, same issue seen in both cases.
Is there a work around for this issue?

[Simon Quigley (tsimonq2)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1340734

and any other logs that are relevant for this particular issue.

[Steven Clarkson (sclarkson)]

I'm seeing this doing an EFI OEM install on 16.04.4 server. I've attached the relevant part of the install syslog.

The problem is exactly as described in the original post. It is installing oem-config-debconf, which depends on ubiquity, which recommends grub-pc | grub | grub-efi. As grub-efi is not installed, (only grub-efi-amd64 is in my case), this causes a conflict.

This doesn't happen in the desktop version because ubiquity is already installed in the target system.

The grub-efi-[arch] packages should probably have a common Provides that ubiquity can recommend instead of the grub-efi package.

[Launchpad Janitor (janitor)]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]