** Description changed: + [Impact] + + + [Test case] + 1) boot in EFI mode + TEST) Unmount /sys/firmware/efi/efivars and/or remove efivars module. + 2) Run archdetect. + + [Regression potential] + If efivars or vars don't get mounted (use of another init system than systemd, or lack of the efivars kernel module); the detection code will fail to see that the system is in EFI mode and installation will proceed in legacy mode. + + -- + After installing 16.04 (upgrade or re-install), I get this exception on login. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.12+0.8-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootEFIContents: - fw - fwupx64.efi + fw + fwupx64.efi Date: Mon May 16 09:28:29 2016 Df: - Filesystem 1K-blocks Used Available Use% Mounted on - /dev/sdb2 208735776 11061044 187048532 6% / - /dev/sr0 1451056 1451056 0 100% /cdrom - udev 7894540 0 7894540 0% /dev - tmpfs 1581840 9536 1572304 1% /run + Filesystem 1K-blocks Used Available Use% Mounted on + /dev/sdb2 208735776 11061044 187048532 6% / + /dev/sr0 1451056 1451056 0 100% /cdrom + udev 7894540 0 7894540 0% /dev + tmpfs 1581840 9536 1572304 1% /run EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: efibootmgr: EFI variables are not supported on this system. ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: - dpkg 1.18.4ubuntu1 - apt 1.2.10ubuntu1 + dpkg 1.18.4ubuntu1 + apt 1.2.10ubuntu1 SourcePackage: shim-signed Title: package shim-signed 1.12+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed: [Impact] - + Some systems which do not correctly support EFI variables or have an incomplete implementation of the EFI spec may fail to install due to efibootmgr being unable to set BootEntry although archdetect reports the system being booted in EFI mode. [Test case] 1) boot in EFI mode TEST) Unmount /sys/firmware/efi/efivars and/or remove efivars module. 2) Run archdetect. [Regression potential] If efivars or vars don't get mounted (use of another init system than systemd, or lack of the efivars kernel module); the detection code will fail to see that the system is in EFI mode and installation will proceed in legacy mode. -- After installing 16.04 (upgrade or re-install), I get this exception on login. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.12+0.8-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootEFIContents: fw fwupx64.efi Date: Mon May 16 09:28:29 2016 Df: Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdb2 208735776 11061044 187048532 6% / /dev/sr0 1451056 1451056 0 100% /cdrom udev 7894540 0 7894540 0% /dev tmpfs 1581840 9536 1572304 1% /run EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: efibootmgr: EFI variables are not supported on this system. ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: shim-signed Title: package shim-signed 1.12+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582320 Title: libdebian-installer uses a different detection method for EFI than efivar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdebian-installer/+bug/1582320/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
