As I understand it the reason you don't have your ESP mounted at
/boot/efi is because you are sharing the disk between the Ubuntu host
system and the Windows guest VM, and therefore it's not safe to have it
mounted read-write on the host.
This is not a configuration that we can support. We must be able to
update the contents of the ESP at package upgrade time, in order to
ensure your bootloader is up-to-date and secure (including in the case
of disabling secureboot due to binary drivers - because this "disabling"
is still done through shim itself). Even if the shim and grub packages
were improved to be able to autodiscover and mount the ESP when needed,
the fact that you have the ESP "locked" by another OS makes this
impossible in your case.
I think you should create a separate ESP exclusively for Ubuntu; or,
barring that, you should make sure you stop your VM and mount the ESP
before running upgrades.
** Changed in: shim-signed (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750418
Title:
package shim-signed 1.33.1~16.04.1+13-0ubuntu2 failed to
install/upgrade: subprocess installed post-installation script
returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1750418/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
