Comment 8 for bug 1469995

You should be able to fix this by either:

1) Not agreeing to remove grub-efi-amd64-signed but instead waiting for an update for it (and filing a bug pointing out that it is unavailable as appropriate) - but of course I appreciate that users don't magically know this and shouldn't have to.

2) Later installing grub-efi-amd64-signed again.

If the second fix doesn't work, please report the output of "apt-cache policy grub-efi-amd64 grub-efi-amd64-signed".

There was a short window of a few hours just after the grub2 update was released on 8 July when the signed package was not released concurrently and apt-get would have (wrongly) recommended removal of the signed package as a consequence. This was due to a process issue. Since then though, the problem should not recur as the grub-efi-amd64-signed was released after a few hours. However manual recovery is required (unfortunately) for those affected by using the second step above.

So I'm marking this Fix Released as it should be now fixed, but if it is not please explain and reopen.