** Summary changed:
- package shim-signed 1.35+13-0ubuntu2 failed to install/upgrade: installed
shim-signed package post-installation script subprocess returned error exit
status 1
+ package shim-signed 1.35+13-0ubuntu2 failed to install/upgrade: installed
shim-signed package post-installation
On Sat, Jun 02, 2018 at 04:16:45AM -, Willem Hobers wrote:
> So, did I do something wrong when I installed 18.10?
No, this is a known bug in ubiquity which is targeted for fixing in
18.04.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
So, did I do something wrong when I installed 18.10?
And is there anything else I can provide to help?
Op vr 1 jun. 2018 22:25 schreef Steve Langasek :
> > Ubiquity seems to have decided that it was installing on a uefi-
> machine.
>
> And it was almost certainly correct, but the installation of
> Ubiquity seems to have decided that it was installing on a uefi-
machine.
And it was almost certainly correct, but the installation of the UEFI
bootloader failed because your disk did not have an EFI System Partition
to install to. Your 18.10 install was only bootable afterwards because
you pre
Hi Steve,
I really don't know.
I did a clean install of xubuntu 18.10 (for testing purposes) on an
existing partition on a laptop which also has 18.04 on another partition.
That 18.10 installation ended with an error at the very end (ubiquity
complained about not being able to install grub 2). Ub
Your bug report shows that this is an upgrade of the shim-signed
package. How/why do you have the shim-signed package installed, if your
system is not booted in UEFI mode (according to the output of
efibootmgr) and you do not have an EFI system partition mounted at
/boot/efi?
** Changed in: shim-s
