[Bug 1340734] Re: oem-config missing from installed system after OEM mode setup using EFI boot
Cam Scott
cam.scott at iinet.net.au
Fri Apr 17 03:57:01 UTC 2015
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?
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1340734
Title:
oem-config missing from installed system after OEM mode setup using
EFI boot
Status in ubiquity package in Ubuntu:
New
Bug description:
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>.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1340734/+subscriptions
More information about the foundations-bugs
mailing list